[
https://issues.apache.org/jira/browse/NIFI-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423801#comment-15423801
]
ASF subversion and git services commented on NIFI-2566:
-------------------------------------------------------
Commit e42ea9ad457c5b5a1d2da5fa3d3494aacb0cb8d4 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=e42ea9a ]
NIFI-2566: Refactored to allow just the Leader Election Manager to be
responsible for determining who is the Cluster Coordinator
NIFI-2566: Removed storage of cluster roles from heartbeats and
NodeConnectionStatus; use LeaderElectionManager to determine roles instead
NIFI-2566: Updated Heartbeats so that if a node is out-of-sync with cluster
topology, cluster coordinator will provide updated information back to the nodes
NIFI-2566: Fixed issue that prevented standalone instance from starting by
creating a standalone-instance version of the Leader Election Manager. Also
added Controller Service enabled/disabled state to fingerprint rather than
attempting to update the state when joining the cluster, as the implementation
was incorrect and the correct implementation will be a rather significant
effort that doesn't have to happen for 1.0.0 release
This closes #866
Signed-off-by: jpercivall <[email protected]>
> Clustered Nodes can become out of sync regarding which node is coordinator
> --------------------------------------------------------------------------
>
> Key: NIFI-2566
> URL: https://issues.apache.org/jira/browse/NIFI-2566
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally, I will see the UI telling me that no Cluster Coordinator has
> been elected. However, I can see in the logs that the node is sending
> heartbeats to the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
