Stuck Thread Monitor?

[Sven Davison <sv...@gmail.com>]

I have a custom processor that has a stuck thread from time to time. Once
the thread's stuck, it fails to process data. Restarting the NiFi instance
is enough to fix it... for a while.

Without changing the processor, is there a way to monitor stuck threads
w/in NiFi?

Re: Stuck Thread Monitor?

[Joe Witt <jo...@gmail.com>]

Sven,

We do monitor threads which have been given to processors but not
returned.  You can see them through the REST API and UI both on the
processor itself showing thread count and in the summary pages.

For the onTrigger calls of a processor we do not time bound them and
kick out the threads.  We do this for other lifecycle calls like
onScheduled and when stopping but otherwise we let the processor do
its thing and aren't really able to tell if it is 'stuck' and we
should kick it.  We could discuss some sort of a kick-out timer option
for processors.  That said there are some cases where our options are
fairly limited.  We have talked of doing a quarantine mode and then
banning/penalizing the clearly faulty process itself so it cannot just
keep consuming threads.

What sort of behavior as you think through it do you feel like would
make sense if we were to try to be more helpful here?

Thanks
Joe

On Wed, Jul 20, 2016 at 10:09 AM, Sven Davison <sv...@gmail.com> wrote:
> I have a custom processor that has a stuck thread from time to time. Once
> the thread's stuck, it fails to process data. Restarting the NiFi instance
> is enough to fix it... for a while.
>
> Without changing the processor, is there a way to monitor stuck threads w/in
> NiFi?