[
https://issues.apache.org/jira/browse/NIFI-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404674#comment-15404674
]
ASF GitHub Bot commented on NIFI-2419:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/739
@YolandaMDavis thanks - I have rebased against master.
> 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)