[ https://issues.apache.org/jira/browse/NIFI-11289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann updated NIFI-11289: ------------------------------------ Fix Version/s: 2.0.0 1.21.0 Resolution: Fixed Status: Resolved (was: Patch Available) > 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: 2.0.0, 1.21.0, 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)