Hi Joe, Thanks for the quick reply. Yes, the processor keeps running on a single thread (even after stopping). And the number remains there even after stopping. Today, it happened on my customized putHDFS processor. Only thing different in this processor is - I have added an additional attribute that tells if the processor created the directory while loading the file on HDFS. I don't think this should be the issue though.
Regards, Manish On Wed, Nov 30, 2016 at 7:05 PM, Joe Witt <[email protected]> wrote: > Manish > > When it is stuck do you see a number in the top right corner of the > processor? When you stop it does the number remain? That number is > telling you how many threads are still executing. Which processor are > we talking about? When it is in the stuck state can you please run > bin/nifi.sh dump. If you can then share the nifi-bootstrap.log that > would aid us in narrowing in on a possible cause. > > Thanks > Joe > > On Wed, Nov 30, 2016 at 7:02 PM, Manish G <[email protected]> wrote: > > > > Hi, > > > > I have noticed that sometime a flow file gets stuck on a processor for a > > very long time for no reason and then I can not even stop the processor > to > > look at the flow flow file from queue. If I click on stop, then processor > > goes into a state where I cannot start/stop the processor. > > > > On restarting the NiFi, the file gets processed successfully and routed > to > > success queue. I checked in App log, but everything seems to be normal > for > > the flow file. I don't see anything mysterious in provenance too (except > > that queue time is in hours). > > > > Has anyone else faced a similar issue? What else should I check to > identify > > the root cause for this? > > > > Thanks, > > Manish > -- *With Warm Regards,* *Manish*
