[
https://issues.apache.org/jira/browse/NIFI-10226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566365#comment-17566365
]
Joe Witt commented on NIFI-10226:
---------------------------------
If you look in the nifi-app.log there is probably more interesting information
like timeouts/etc.. I suspect it is taking so long and hanging...and then not
responding appropriately.
An alternative way of clearing that queue is to stop feeding it new data by
stopping upstream components/processors then changing the queue settings to
expire based on age. Let it clear out then return the settings to how you want
them. We will need to figure out if massive queue emptying needs work.
> Empty Queue 1'500'000 flowfiles - NiFi GUI HTTP Error 503
> ---------------------------------------------------------
>
> Key: NIFI-10226
> URL: https://issues.apache.org/jira/browse/NIFI-10226
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
> Affects Versions: 1.15.3
> Environment: 8-Node cluster
> Reporter: Josef Zahner
> Priority: Major
> Attachments: Screenshot 2022-07-13 at 13.46.23.png
>
>
> We have a ListSFTP processor which produces 1'500'000 flowfiles as output.
> When we try to "Empty Queue" it takes multiple minutes and the GUI shows a
> HTTP 503 error during that period. We can't open the GUI again until the
> deletion is complete. Those flowfiles are all on the primary node and not
> load balanced within the cluster. Below is the final GUI message. The
> intermediate message looks similar but without the removed string.
> !Screenshot 2022-07-13 at 13.46.23.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
