Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/721
I have played with both Put and Get processors and it seems to work fine.
However, when stopping/starting processors to change properties (to test
batching and performances), I got in a situation with this exception:
````
2016-10-03 23:32:42,633 WARN [Timer-Driven Process Thread-4]
o.a.n.c.t.ContinuallyRunProcessorTask Administratively Yielding
PutIgniteCache[id=4d80623c-0157-1000-0000-0000179dcc8f] due to uncaught
Exception: java.lang.IllegalStateException: Data streamer has been closed.
2016-10-03 23:32:42,634 WARN [Timer-Driven Process Thread-4]
o.a.n.c.t.ContinuallyRunProcessorTask
java.lang.IllegalStateException: Data streamer has been closed.
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.enterBusy(DataStreamerImpl.java:355)
~[na:na]
at
org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl.addData(DataStreamerImpl.java:489)
~[na:na]
at
org.apache.nifi.processors.ignite.cache.PutIgniteCache.onTrigger(PutIgniteCache.java:274)
~[na:na]
at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
~[nifi-api-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1060)
~[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:123)
[nifi-framework-core-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
[na:1.8.0_77]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
[na:1.8.0_77]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
[na:1.8.0_77]
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
[na:1.8.0_77]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_77]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_77]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_77]
````
It was not possible to get the flow back to OK unless restarting NiFi. I
believe something is not closed correctly.
To reproduce, take this template, run all processors, everything should be
OK, stop GetIgnite processor and restart it, do the same with PutIgnite. You
should get the error.
Here is the template I use:
https://gist.github.com/pvillard31/8a0c1d0344bf5bdfdf4cd460e936905c
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
