Also, if you care to share the code for you processor we’ll be happy to look and help you find the problem. As Joe pointed out we make every possible attempt to stop it, but if your custom code is blocking and does not react to interrupts then there is not much we can do stoping short of Thread.stop (which is something we are reluctantly contemplating)
Cheers Oleg > On Jul 22, 2016, at 3:47 PM, Joe Witt <joe.w...@gmail.com> wrote: > > Devin, > > In the more recent versions of NiFi attempts to stop the processor > which are not successful after some period of time (I think 30 > seconds) should result in the process being killed if possible and > NiFi should then move on again. > > What version are you on? > > Thanks > Joe > > On Fri, Jul 22, 2016 at 3:32 PM, Devin Fisher > <devin.fis...@perfectsearchcorp.com> wrote: >> Mostly a general questions. The processor in question is a custom made one >> that is obviously misbehaving. I'm looking into why the process doesn't stop >> like like normal but I was wondering if there was a way to "force" stop a >> process (kill the processor)? I know I can restart the nifi process to stop >> the process but I was hoping for a way that was a little less drastic. >> >> Devin >
