Were you disabling the processor or just stopping it? I've found with the scripted processors they will get in an odd state and that's the only way to reset it.
Shawn ________________________________ From: Boris Tyukin <bo...@boristyukin.com> Sent: Tuesday, May 22, 2018 3:07:36 PM To: users@nifi.apache.org Subject: Re: InvokeScriptedProcessor from a shared folder well it works now...after I recreated processor 3 times and was changing parameters back and forth and now that error is gone. we did not change permissions on nfs or file so not sure why nifi did not like it at first. On Tue, May 22, 2018 at 3:32 PM, Boris Tyukin <bo...@boristyukin.com<mailto:bo...@boristyukin.com>> wrote: Hello, I created a custom groovy processor and saved it in a file. That file was placed on NFS share and I pointed NiFi's InvokeScriptedProcessor to it. When I started a processor, I got a weird error that it failed custom validation. If I copy that file out of NFS to a local directory, it works fine. It seems that NiFi is trying to obtain a file lock or something that NFS does not support. Can someone shed some light on this? We were hoping to keep scripted processors on NFS so they accessible from all the nodes and also deployed to a single place. Thanks, Boris
