You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@nifi.apache.org by Igor Kravzov <ig...@gmail.com> on 2016/05/06 21:16:54 UTC
PutElasticsearch error
I configured ES processor with ES cluster name and 2 hosts. But it fails to
inject data with exceptions below. What can be wrong?
I have another workflow where I use PostHTTP processor to one of the nodes
and the same port and it works.
2016-05-06 16:36:39,291 ERROR [Timer-Driven Process Thread-3]
o.a.n.p.elasticsearch.PutElasticsearch
PutElasticsearch[id=4fa011f7-64ab-4b83-b248-94b51cbc76c1] Failed to insert
into Elasticsearch due to None of the configured nodes are available:
[{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
{#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]. More detailed
information may be available in the NiFi logs.:
NoNodeAvailableException[None of the configured nodes are available:
[{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
{#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]]
2016-05-06 16:36:39,293 ERROR [Timer-Driven Process Thread-3]
o.a.n.p.elasticsearch.PutElasticsearch
org.elasticsearch.client.transport.NoNodeAvailableException: None of the
configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/
10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]
at
org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)
~[elasticsearch-2.1.0.jar:2.1.0]
at
org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:188)
~[nifi-elasticsearch-processors-0.6.1.jar:0.6.1]
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
[nifi-api-0.6.1.jar:0.6.1]
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1059)
[nifi-framework-core-0.6.1.jar:0.6.1]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
[nifi-framework-core-0.6.1.jar:0.6.1]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
[nifi-framework-core-0.6.1.jar:0.6.1]
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
[nifi-framework-core-0.6.1.jar:0.6.1]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
[na:1.7.0_60]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
[na:1.7.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
[na:1.7.0_60]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
[na:1.7.0_60]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[na:1.7.0_60]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[na:1.7.0_60]
at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
Re: PutElasticsearch error
Posted by Igor Kravzov <ig...@gmail.com>.
Oh. Thanks I will try.
On May 6, 2016 5:21 PM, "Pierre Villard" <pi...@gmail.com>
wrote:
> Hi Igor,
>
> I believe ES processor uses port 9300 (transport port) and not 9200 port
> (http port)
>
> Pierre.
>
> 2016-05-06 23:16 GMT+02:00 Igor Kravzov <ig...@gmail.com>:
>
>> I configured ES processor with ES cluster name and 2 hosts. But it fails
>> to inject data with exceptions below. What can be wrong?
>> I have another workflow where I use PostHTTP processor to one of the
>> nodes and the same port and it works.
>>
>> 2016-05-06 16:36:39,291 ERROR [Timer-Driven Process Thread-3]
>> o.a.n.p.elasticsearch.PutElasticsearch
>> PutElasticsearch[id=4fa011f7-64ab-4b83-b248-94b51cbc76c1] Failed to insert
>> into Elasticsearch due to None of the configured nodes are available:
>> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
>> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]. More detailed
>> information may be available in the NiFi logs.:
>> NoNodeAvailableException[None of the configured nodes are available:
>> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
>> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]]
>> 2016-05-06 16:36:39,293 ERROR [Timer-Driven Process Thread-3]
>> o.a.n.p.elasticsearch.PutElasticsearch
>> org.elasticsearch.client.transport.NoNodeAvailableException: None of the
>> configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/
>> 10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200
>> }]
>> at
>> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:188)
>> ~[nifi-elasticsearch-processors-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>> [nifi-api-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1059)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> [na:1.7.0_60]
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [na:1.7.0_60]
>> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
>>
>
>
Re: PutElasticsearch error
Posted by Igor Kravzov <ig...@gmail.com>.
Yes, it worked. Thanks.
On Fri, May 6, 2016 at 5:27 PM, Matt Burgess <ma...@gmail.com> wrote:
> Pierre is correct
>
> Sent from my iPhone
>
> On May 6, 2016, at 5:20 PM, Pierre Villard <pi...@gmail.com>
> wrote:
>
> Hi Igor,
>
> I believe ES processor uses port 9300 (transport port) and not 9200 port
> (http port)
>
> Pierre.
>
> 2016-05-06 23:16 GMT+02:00 Igor Kravzov <ig...@gmail.com>:
>
>> I configured ES processor with ES cluster name and 2 hosts. But it fails
>> to inject data with exceptions below. What can be wrong?
>> I have another workflow where I use PostHTTP processor to one of the
>> nodes and the same port and it works.
>>
>> 2016-05-06 16:36:39,291 ERROR [Timer-Driven Process Thread-3]
>> o.a.n.p.elasticsearch.PutElasticsearch
>> PutElasticsearch[id=4fa011f7-64ab-4b83-b248-94b51cbc76c1] Failed to insert
>> into Elasticsearch due to None of the configured nodes are available:
>> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
>> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]. More detailed
>> information may be available in the NiFi logs.:
>> NoNodeAvailableException[None of the configured nodes are available:
>> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
>> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]]
>> 2016-05-06 16:36:39,293 ERROR [Timer-Driven Process Thread-3]
>> o.a.n.p.elasticsearch.PutElasticsearch
>> org.elasticsearch.client.transport.NoNodeAvailableException: None of the
>> configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/
>> 10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200
>> }]
>> at
>> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)
>> ~[elasticsearch-2.1.0.jar:2.1.0]
>> at
>> org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:188)
>> ~[nifi-elasticsearch-processors-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
>> [nifi-api-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1059)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
>> [nifi-framework-core-0.6.1.jar:0.6.1]
>> at
>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>> [na:1.7.0_60]
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [na:1.7.0_60]
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [na:1.7.0_60]
>> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
>>
>
>
Re: PutElasticsearch error
Posted by Matt Burgess <ma...@gmail.com>.
Pierre is correct
Sent from my iPhone
> On May 6, 2016, at 5:20 PM, Pierre Villard <pi...@gmail.com> wrote:
>
> Hi Igor,
>
> I believe ES processor uses port 9300 (transport port) and not 9200 port (http port)
>
> Pierre.
>
> 2016-05-06 23:16 GMT+02:00 Igor Kravzov <ig...@gmail.com>:
>> I configured ES processor with ES cluster name and 2 hosts. But it fails to inject data with exceptions below. What can be wrong?
>> I have another workflow where I use PostHTTP processor to one of the nodes and the same port and it works.
>>
>> 2016-05-06 16:36:39,291 ERROR [Timer-Driven Process Thread-3] o.a.n.p.elasticsearch.PutElasticsearch PutElasticsearch[id=4fa011f7-64ab-4b83-b248-94b51cbc76c1] Failed to insert into Elasticsearch due to None of the configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]. More detailed information may be available in the NiFi logs.: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]]
>> 2016-05-06 16:36:39,293 ERROR [Timer-Driven Process Thread-3] o.a.n.p.elasticsearch.PutElasticsearch
>> org.elasticsearch.client.transport.NoNodeAvailableException: None of the configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]
>> at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59) ~[elasticsearch-2.1.0.jar:2.1.0]
>> at org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:188) ~[nifi-elasticsearch-processors-0.6.1.jar:0.6.1]
>> at org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27) [nifi-api-0.6.1.jar:0.6.1]
>> at org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1059) [nifi-framework-core-0.6.1.jar:0.6.1]
>> at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136) [nifi-framework-core-0.6.1.jar:0.6.1]
>> at org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47) [nifi-framework-core-0.6.1.jar:0.6.1]
>> at org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123) [nifi-framework-core-0.6.1.jar:0.6.1]
>> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [na:1.7.0_60]
>> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) [na:1.7.0_60]
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) [na:1.7.0_60]
>> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) [na:1.7.0_60]
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [na:1.7.0_60]
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [na:1.7.0_60]
>> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
>
Re: PutElasticsearch error
Posted by Pierre Villard <pi...@gmail.com>.
Hi Igor,
I believe ES processor uses port 9300 (transport port) and not 9200 port
(http port)
Pierre.
2016-05-06 23:16 GMT+02:00 Igor Kravzov <ig...@gmail.com>:
> I configured ES processor with ES cluster name and 2 hosts. But it fails
> to inject data with exceptions below. What can be wrong?
> I have another workflow where I use PostHTTP processor to one of the nodes
> and the same port and it works.
>
> 2016-05-06 16:36:39,291 ERROR [Timer-Driven Process Thread-3]
> o.a.n.p.elasticsearch.PutElasticsearch
> PutElasticsearch[id=4fa011f7-64ab-4b83-b248-94b51cbc76c1] Failed to insert
> into Elasticsearch due to None of the configured nodes are available:
> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]. More detailed
> information may be available in the NiFi logs.:
> NoNodeAvailableException[None of the configured nodes are available:
> [{#transport#-1}{10.1.128.50}{BPIW01A/10.1.128.50:9200},
> {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]]
> 2016-05-06 16:36:39,293 ERROR [Timer-Driven Process Thread-3]
> o.a.n.p.elasticsearch.PutElasticsearch
> org.elasticsearch.client.transport.NoNodeAvailableException: None of the
> configured nodes are available: [{#transport#-1}{10.1.128.50}{BPIW01A/
> 10.1.128.50:9200}, {#transport#-2}{10.1.128.51}{BPIW02A/10.1.128.51:9200}]
> at
> org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:283)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:347)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)
> ~[elasticsearch-2.1.0.jar:2.1.0]
> at
> org.apache.nifi.processors.elasticsearch.PutElasticsearch.onTrigger(PutElasticsearch.java:188)
> ~[nifi-elasticsearch-processors-0.6.1.jar:0.6.1]
> at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
> [nifi-api-0.6.1.jar:0.6.1]
> at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1059)
> [nifi-framework-core-0.6.1.jar:0.6.1]
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
> [nifi-framework-core-0.6.1.jar:0.6.1]
> at
> org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
> [nifi-framework-core-0.6.1.jar:0.6.1]
> at
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
> [nifi-framework-core-0.6.1.jar:0.6.1]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> [na:1.7.0_60]
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> [na:1.7.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> [na:1.7.0_60]
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> [na:1.7.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_60]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_60]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_60]
>