[
https://issues.apache.org/jira/browse/NIFI-9017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406086#comment-17406086
]
ASF subversion and git services commented on NIFI-9017:
-------------------------------------------------------
Commit d90ef0675290f8d7cdb07bf33be3a1e01576145a in nifi's branch
refs/heads/main from markap14
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d90ef06 ]
NIFI-9017: Update Load Balanced Connection logic so that if a node connects to
the cluster with a different load balancing hostname/port, it starts sending to
the new endpoint instead of failing to send to the old endpoint (#5287)
Self-merging based on +1 feedback from multiple active community members who
have reviewed & tested code
> If a node's load balance host/port is updated, other nodes stop sending data
> ----------------------------------------------------------------------------
>
> Key: NIFI-9017
> URL: https://issues.apache.org/jira/browse/NIFI-9017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I have a 3-node cluster. On one of the nodes, I stopped it, changed the load
> balance host from localhost to 127.0.0.1, and also changed the load balancing
> port, and restarted. As a result, all other nodes in the cluster stopped
> sending data to the node and started generating ConnectExceptions. The other
> nodes in the cluster should still be able send after a load balance
> hostname/port is changed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
