You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Mark Payne (JIRA)" <ji...@apache.org> on 2018/10/09 16:25:00 UTC

[jira] [Updated] (NIFI-5672) Node Identifier comparison can result in duplicate nodes in cluster when upgrading to newest version

     [ https://issues.apache.org/jira/browse/NIFI-5672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Payne updated NIFI-5672:
-----------------------------
    Status: Patch Available  (was: Open)

> Node Identifier comparison can result in duplicate nodes in cluster when upgrading to newest version
> ----------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-5672
>                 URL: https://issues.apache.org/jira/browse/NIFI-5672
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 1.8.0
>
>
> Now that the Load Balancing capability has been merged to master, upgrading old clusters works okay as long as the Load Balancing port is properly specified. However, if the cluster is restarted without specifying the port, and the port is then changed, we get duplicate representations of the nodes in the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)