nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Gilman (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NIFI-6488) NiFi web interface often non-responsive
Date Thu, 25 Jul 2019 20:51:00 GMT

    [ https://issues.apache.org/jira/browse/NIFI-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893120#comment-16893120
] 

Matt Gilman commented on NIFI-6488:
-----------------------------------

It appears you've tried to attach an image but it didn't work.

Is the browser itself unresponsive or is the browser issuing requests that are not returning?
Try opening the browsers Developer Tools and looking at the Network tab to see if there are
any Pending requests. If so, try taking a thread dump  [1] and looking at any threads name
NiFi Web Server. The thread dump should go to the nifi-bootstrap.log by default.

[1] ./bin/nifi.sh dump

> 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
>
> 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)

Mime
View raw message