[
https://issues.apache.org/jira/browse/NIFI-6779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953844#comment-16953844
]
ASF subversion and git services commented on NIFI-6779:
-------------------------------------------------------
Commit b004f1f94c5857e89d4410153f43dc0000709ff5 in nifi's branch
refs/heads/master from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b004f1f ]
NIFI-6779: When resolving node identifier, if NodeIdentifier has a different
value for hostname/port for web api or cluster protocol, assume that node is
correct about itself instead of assuming that Cluster Coordinator knows best
about the other node
NIFI-6779: Remove any conflicting Node Identifiers when a new Node ID is
encountered
This closes #3819
> When restarting a node, if HTTP hostname/port or Cluster Protocol
> hostname/port changes, the node is recognized as new
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: NIFI-6779
> URL: https://issues.apache.org/jira/browse/NIFI-6779
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If we have a cluster and shutdown a node, when it restarts, if its HTTP[s]
> hostname/port has changed or the Cluster Protocol hostname/port has changed,
> we see the old node and the new node in the Cluster, with the old node being
> disconnected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
