Our production nifi cluster is exhibiting repeated problems with threads that do not end. It is happening with processors that have complex configurations and dependencies (ConsumeAMQP), and - more troubling - it is also occurring periodically for simple processors like ControlRate. I’ll have a Control processor sitting in a running state with no active running thread,I select Stop on that processor, get a thread I presume to be responsible for stopping the processor, and that thread will never end. This renders my processor in a useless state - not stopped, not really running, and not accessible to reconfigure.
I read a blog by Pierre Villard on using nifi.sh for thread dumps. I’ll dig into that. My questions: 1. In a cluster, is there anything I can use in the UI to tell me which cluster node hosts the bad thread? Digging through thread dumps from multiple cluster nodes seems impractical, and I’m hoping there’s a way to zero in on a node. 2. What nifi system resources in my configuration influence the management and well-being of these threads? 3. Has anyone debugged such a thread issue in a clustered nifi environment, and if so can you offer any tips based on your experience? Thanks in advance for any help. Jim
