ExecuteScript will certainly support a clustered NiFi environment. Is the processor actually processing files on both nodes, but only failing on one? Is it possible that the cluster's flow routes files through the processor only on one node?
Also, can you share your script? It sounds like you have an InputStreamCallback not getting closed, or maybe an out of date flowfile reference. On Thu, Aug 3, 2017 at 6:54 AM, wildo <willy.de...@moserit.com> wrote: > James- one last question. Does ExecuteScript support clustered NIFI > instances? I keep getting this exception ONLY from the second node (2 of 2) > in our cluster: > > "StandardFlowFileRecord ... already in use for active callback or an > InputStream created by ProcessSession.read(FlowFile) has not been closed in > <script>" > > It sure seems to me that I have TWO flowfiles- one for each node in the > cluster, and therefore I don't know why the session object for the > ExecuteScript process would be sharing a flowfile between the two nodes. I > think my understanding on this is limited. > > > > -- > View this message in context: http://apache-nifi-developer- > list.39713.n7.nabble.com/Dynamic-attributes-on-repeating-capture-groups- > tp16540p16569.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
