[ https://issues.apache.org/jira/browse/NIFI-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397938#comment-15397938 ]
ASF GitHub Bot commented on NIFI-2419: -------------------------------------- GitHub user markap14 opened a pull request: https://github.com/apache/nifi/pull/739 NIFI-2419: Ensure that if a node is disconnected that we unregister f… …or 'cluster coordinator' and 'primary node' roles by updating FlowController to know that it is disconnected. Also removed dead code that was needed in the master-worker clustering paradigm but not for zero-master-clustering You can merge this pull request into a Git repository by running: $ git pull https://github.com/markap14/nifi NIFI-2419 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/739.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #739 ---- ---- > Node could be elected Cluster Coordinator when disconnected from cluster > ------------------------------------------------------------------------ > > Key: NIFI-2419 > URL: https://issues.apache.org/jira/browse/NIFI-2419 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.0.0 > Reporter: Mark Payne > Assignee: Mark Payne > Priority: Blocker > Fix For: 1.0.0 > > > In my cluster, I see the following Node events for a particular node: > 07/28/2016 06:17:29 UTC: Acquired role [Cluster Coordinator] > 07/28/2016 04:53:30 UTC: Node Status changed from CONNECTING to DISCONNECTED > due to org.apache.nifi.controller.UninheritableFlowException: Failed to > connect node to cluster because local flow is different than cluster flow. > So the Cluster Coordinator role was obtained even though the node is > disconnected. This shouldn't happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)