[
https://issues.apache.org/jira/browse/NIFI-11289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700853#comment-17700853
]
ASF subversion and git services commented on NIFI-11289:
--------------------------------------------------------
Commit f571d5704e11a8f4083f41f6e986539f922dffa0 in nifi's branch
refs/heads/support/nifi-1.x from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f571d5704e ]
NIFI-11289: Avoid obtaining read locks on queues when fetching Group Status,
except in those few specific situations where it's needed.
This closes #7046
Signed-off-by: David Handermann <exceptionfact...@apache.org>
> NiFi UI blocks on read access to FlowFile Queues
> ------------------------------------------------
>
> Key: NIFI-11289
> URL: https://issues.apache.org/jira/browse/NIFI-11289
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When the NiFi UI makes a request for a given Process Group or its status, the
> backend must obtain Read Locks on the FlowFile Queues in order to provide the
> information back to the UI.
> This results in a sluggish UI whenever there are a lot of queues with a lot
> of FlowFiles flowing. And in a case where we drop huge numbers of FlowFiles
> or add huge numbers of FlowFiles to queue (for instance, as a result of
> SplitJson) that lock can be held for quite a while, making the UI block
> arbitrarily long.
> The Read Locks, however, are not necessary for any of the requests that the
> UI makes for the canvas. They are necessary only for the Status History of
> the Connection/Queue. And for backward compatibility we should also make it
> available to Reporting Tasks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
