Hey Mark, Changing the scheduling doesn't seem to make a difference.
I have noticed some instances where a nifi.sh dump causes a switch of the primary node and that unleashes the stuck processor but still not clear why it happens. I took a thread dump of the primary node while the thing was happening. Will upload to gist soon. Cheers On Thu, Nov 16, 2017 at 2:07 AM, Mark Payne <marka...@hotmail.com> wrote: > Andre, > > So I am guessing that backpressure is not an issue then if you're not > seeing it run :) > Have you tried reducing the scheduling period from 5 mins to something > like 5 seconds? > Of course, you may not want to actually be running it every 5 seconds in a > production environment, > but I am curious if it would cause it to start running or not... > > > On Nov 15, 2017, at 10:02 AM, Andre <andre-li...@fucs.org> wrote: > > > > Mark, > > > > Timer driven, Primary Node, 5 min > > Yield is set to 1 sec > > Backpressure = 10k flows or 1GB > > nifi.administrative.yield.duration=30 sec > > > > Cheers > > > > > > On Thu, Nov 16, 2017 at 1:32 AM, Mark Payne <marka...@hotmail.com> > wrote: > > > >> Hey Andre, > >> > >> I have not seen this personally. Can you share how you have the > Scheduling > >> Tab configured? > >> Is it set to Timer-Driven with a period of "0 secs"? Also, what is the > >> Yield Duration set to? > >> Is there any backpressure configured on any of the outbound connections? > >> Additionally, what is the value of the "nifi.administrative.yield. > duration" > >> property in nifi.properties? > >> > >> Sorry - I know that's a barrage of questions. Hopefully it's something > >> easy that's just being overlooked, though :) > >> > >> -Mark > >> > >>> On Nov 15, 2017, at 4:58 AM, Andre <andre-li...@fucs.org> wrote: > >>> > >>> Folks, > >>> > >>> Has anyone ever seen a situation where ListSFTP simply stops working? > >>> > >>> I have observed a few occurrences of seems to be some weird bug. > >>> > >>> Symptoms are: > >>> > >>> - Processor looks healthy (i.e. no bulletins) > >>> - State is stalled (i.e. no changes to new files or timestamps) > >>> - No signs of a stuck thread (i.e. processor doesn't display a thread > >> count) > >>> - UI displays processor "Task count = 0/0" > >>> - Neither stopping > starting nor stopping > disabling > enabling > > >>> starting processor seems to make a difference. > >>> > >>> Has anyone seen this? > >>> > >>> Cheers > >> > >> > >
