[
https://issues.apache.org/jira/browse/NIFI-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15388173#comment-15388173
]
ASF GitHub Bot commented on NIFI-2292:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/701
NIFI-2292: Funnel all cluster node status changes through the cluster
coordinator…
… instead of having each node broadcast changes to the whole cluster. This
gives us the ability to increment the updateId consistently without race
conditions.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2292
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/701.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 #701
----
commit 03942d0091e6adc213dc42e3c81725ab5ca257fa
Author: Mark Payne <[email protected]>
Date: 2016-07-21T18:30:08Z
NIFI-2292: Funnel all cluster node status changes through the cluster
coordinator instead of having each node broadcast changes to the whole cluster.
This gives us the ability to increment the updateId consistently without race
conditions.
----
> Nodes in cluster sometimes become out-of-sync with actual 'connection state'
> of node
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2292
> URL: https://issues.apache.org/jira/browse/NIFI-2292
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> Occasionally I'll see a node that has a different view of the cluster than
> other nodes. Right now I'm actually seeing "node 1" think it's in
> 'CONNECTING' state while nodes 2-5 think we have 5/5 nodes connected.
> This also can result in a node that is elected cluster coordinator and then
> has that role revoked can continually monitor for heartbeats, even though it
> won't receive them since it's not the coordinator anymore. This results in
> continually logging a message like "Failed to retrieve any new heartbeat
> information for nodes. Will not make any decisions based on heartbeats."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
