[
https://issues.apache.org/jira/browse/NIFI-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266142#comment-15266142
]
Puspendu Banerjee commented on NIFI-1743:
-----------------------------------------
Does this relate to
https://cwiki.apache.org/confluence/display/NIFI/Zero+Master+Clustering ?
How are we trying to attack this problem ? Is distributed consensus is
something that we are trying to achieve?
Is there any work in progress?
Are you planning to build from scratch or planning to use any readily available
implementation?
> Allow Heartbeats to be replicated to all nodes in the cluster
> -------------------------------------------------------------
>
> Key: NIFI-1743
> URL: https://issues.apache.org/jira/browse/NIFI-1743
> Project: Apache NiFi
> Issue Type: Task
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> Originally, we had planned to use ZooKeeper to store node heartbeats.
> However, this caused quite a bit of concern within the community and provided
> a fairly poor user experience if we lost the quorum, as the state of the
> entire NiFi cluster is no longer known since we are unable to read from
> ZooKeeper.
> As an alternative, we will instead send a heartbeat message to each node in
> the cluster. The Elected Leader will be responsible for determining if a
> particular node is to be disconnected due to a lack of heartbeat. All other
> nodes will then be notified of this; if Node X is deemed disconnected and
> then sends a heartbeat to Node Z, Node Z should respond by notifying Node X
> that it was disconnected. If Node X then receives many of these responses
> because it is heartbeating to many nodes, that is okay - it should be implied
> idempotent behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
