[jira] [Comment Edited] (NIFI-9017) If a node's load balance host/port is updated, other nodes stop sending data

["Jens M Kofoed (Jira)" <ji...@apache.org>]

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

Jens M Kofoed edited comment on NIFI-9017 at 8/6/21, 7:33 AM:
--------------------------------------------------------------

Changing hostname localhost to ip 127.0.0.1 is the same. In both cases it will only listen for connection from the localhost and other nodes will not be able to connect. Use the real ip address for the node which the other nodes can reach it at

Check which ip the port binds to


was (Author: jmkofoed):
Changing hostname localhost to ip 127.0.0.1 is the same. In both cases it will only listen for connection from the localhost and other nodes will not be able to connect. Use the real ip address for the node which the other nodes can reach it at

> 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
>
> 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)