[
https://issues.apache.org/jira/browse/NIFI-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14977210#comment-14977210
]
Aldrin Piri edited comment on NIFI-730 at 10/27/15 9:35 PM:
------------------------------------------------------------
Correct. Doing a `watch` on curl -s localhost:8080/nifi-api/controller/status
| jq . continuously returns a new clientId every second, even while the UI
hangs on the droplet.
Watching that output, such as the below, for the queue to go to zero and then
refreshing the UI, the canvas loads instantaneously
was (Author: aldrin):
Correct. Doing a `watch` on curl -s localhost:8080/nifi-api/controller/status
| jq . continuously returns a new clientId every second, even while the UI
hangs on the droplet.
> Purge Queue from UI
> -------------------
>
> Key: NIFI-730
> URL: https://issues.apache.org/jira/browse/NIFI-730
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework, Core UI
> Reporter: Brian Ghigiarelli
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments: blocked-ui.dump
>
>
> Making changes to connections between NiFi processors is difficult when data
> is queued up between those processors. A workaround to this data build up is
> to stop both processors, reduce/set the FlowFile Expiration of the connection
> to a low number (e.g., 2 sec), then start the receiving processor to age off
> the data.
> A more user-friendly solution is to provide a "Purge" or "Delete" context
> menu option on the queues to remove the data and/or age it off immediately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
