David Sargrad created NIFI-6488:
-----------------------------------
Summary: NiFi web interface often non-responsive
Key: NIFI-6488
URL: https://issues.apache.org/jira/browse/NIFI-6488
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.9.2
Environment: centos 7
Reporter: David Sargrad
I have been using NiFi for close to a year. Currently most of my experience has
been with building custom processors and prototyping a variety of flows.
Often the NiFi web interface becomes non-responsive. Its typically during a
flow integration phase, where I leave flowfiles sitting in queues, sometimes 3
or 4 queues may be maxed at 10,000 flow files. These are relatively small
flowfiles (perhaps 200 or 300 bytes). Yet, of course, the sum total of the
filled queues is in the tens of megabytes.
I am guessing that the JVM is nearing, or perhaps has exceeded, its maximum
allocated heap size. I'd think that NiFi protects against non-responsive UI's
by shedding load, presenting a warning, or doing something to preserve its
operational state.
What is the best way for me to isolate this issue? I'd like to understand
exactly what drives NiFi to be non-responsive. If there is anything that I can
do to isolate this, and to help the NiFi team make this more robust, I'm glad
to dig.
Its been impossible for me to exactly characterize the conditions that lead to
a non-responsive NiFi UI. However I see this fairly frequently.
!image-2019-07-25-08-23-46-031.png!
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
