Brian,
I'd say managing your own thread pool in general is bad -- but not
necessarily a super terrible thing.
We've done similar things before. It really just comes down to: do the
benefits outweigh the cons?
Thanks
-Mark
------ Original Message ------
From: "Brian Ghigiarelli" <[email protected]>
To: [email protected]
Sent: 4/29/2015 9:14:24 PM
Subject: Thread Management within Processors
Hi all,
Is there a consensus on creating thread pools and managing them within
processors (as opposed to using the Concurrent Tasks to handle thread
management)?
In particular, we've rolled a different version of the GetKafka
processor,
but it doesn't use the getConcurrentTasks() like the current version
does.
Instead, we extend AbstractSessionFactoryProcessor, create our own
thread
pool in onTrigger, and handle shutdowns / restarts with the remaining
lifecycle hooks. In any case, it's outside of the context of the
concurrent tasks managed in NiFi. Goodness / badness?
Thanks,
--
Brian Ghigiarelli
