Unfortunately I can’t seem to even see how it would be possible for NiFi to
tell you that since your custom Processors are running within the same JVM as
NiFi.
Having said that the 800% tells me that you probably have some processor with
custom thread pool where each thread is spinning in the
Hello,
We have a nifi flow with many custom processors (and many processor groups). We
suspect that one or more processors are eating up CPU usage, so we're wondering
if there's an easy way to tell which processor has a heavy load on the CPU.
There are tables to see processors in order of
This brings up NiFi best practices question: whether a developer can use spawn
threads in processors or controller services?
If there are any guidelines , it would be nice to document in developer guide.
Sumanth
Sent from my iPad
> On Oct 26, 2015, at 8:14 AM, Oleg Zhurakousky
Elli,
In the majority of cases what Mark suggested will help you pinpoint
the offending processors.
If it is not clear which are the offending processes/extension then it
can require some fairly involved digging. For such things I have
found the following articles provide good examples of how
