[ 
https://issues.apache.org/jira/browse/NIFI-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034738#comment-17034738
 ] 

ASF subversion and git services commented on NIFI-7117:
-------------------------------------------------------

Commit 65b2a9bc2c91657bc160fe93d6051da95ab5db34 in nifi's branch 
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=65b2a9b ]

NIFI-7117: When SocketLoadBalancedFlowFileQueue creates its array of Queue 
Partitions in the constructor, it added the local partition as the first 
element in that list. This list should be ordered the same across all nodes in 
the cluster. By making the local partition the first in the array, each node 
had a different ordering of these partitions. As a result, Partition by 
Attribute strategy would constantly rebalance flowfiles that it received to 
other node, and Single Node always transferred data to the first partition, 
which was the local node, instead of whichever node should have been the first 
in the list. This commit addresses this issue by instead inserting the local 
partition intot he 'queuePartitions' array based on the local node identifier.

Signed-off-by: Pierre Villard <pierre.villard...@gmail.com>

This closes #4045.


> Load Balance is not working
> ---------------------------
>
>                 Key: NIFI-7117
>                 URL: https://issues.apache.org/jira/browse/NIFI-7117
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.11.1
>            Reporter: Eduardo Mota Fontes
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 1.12.0, 1.11.2
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> Load Balancing is not working on 1.11.1.
> I've tested with a 3 node cluster, GenerateFlowFile on All Nodes and a 
> connection with Single Node Load Balancing. All FlowFiles remains in its node.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to