[
https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16917726#comment-16917726
]
David Sargrad commented on NIFI-6488:
-------------------------------------
[~joewitt] I do understand the need to ensure that the data flow is treated as
the number one concern. However I do believe that there are HMI architectures
that can ensure that this is the case. The current issue that I see seems to be
that the HMI is so tightly coupled to the core data processing application. I
do know there is work afoot to refactor the HMI. I wonder if this includes an
eye towards a design element that further decouples the HMI, from the core.
> 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
> Priority: Major
> Attachments: image-2019-08-28-08-15-51-702.png
>
>
> 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.
>
> I've updated the following picture. Since it did not seem to attach before.
> I've also added a view of the memory and CPU consumption. In this particular
> case I waited for about 30 seconds and eventually the NiFi user interface
> came to life.
> !image-2019-08-28-08-15-51-702.png!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
