[ https://issues.apache.org/jira/browse/NIFI-7999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17230767#comment-17230767 ]
ASF subversion and git services commented on NIFI-7999: ------------------------------------------------------- Commit c79ad1502e7938822e5c10693c294538996f5a61 in nifi's branch refs/heads/main from Mark Payne [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c79ad15 ] NIFI-7999: Do not call NioAsyncLoadBalanceClient.nodeDisconnected() if node was already in a disconnected state. Doing so was resulting in that method being called constantly on startup, and with the synchronization in place that can result in a huge performance hit on startup. Also updated RemoteQueuePartition to move a small predicate into its own method. This was done because the predicate was previously defined within a synchronized method, which meant that invoking that predicate required synchronization. Signed-off-by: Pierre Villard <pierre.villard...@gmail.com> This closes #4657. > NiFi startup can be very slow if using many load balanced connections per node > ------------------------------------------------------------------------------ > > Key: NIFI-7999 > URL: https://issues.apache.org/jira/browse/NIFI-7999 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Reporter: Mark Payne > Assignee: Mark Payne > Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If the "nifi.cluster.load.balance.connections.per.node" property is set to a > large value, cluster startup can take a very long time and use a lot of CPU. > This is especially true if there are many load balanced connections. -- This message was sent by Atlassian Jira (v8.3.4#803005)