You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/22 13:22:20 UTC
[jira] [Commented] (NIFI-2360) Improve robustness of cluster when
relying on embedded zookeeper
[ https://issues.apache.org/jira/browse/NIFI-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15389476#comment-15389476 ]
ASF GitHub Bot commented on NIFI-2360:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/705
NIFI-2360: Leave ZooKeeper running when a node is disconnected. Do no…
…t allow the last node in the cluster to be disconnected. Change ClusterProtocoLHeartbeater to use RetryNTime retry strategy instead of RetryForever because web requests could block on this
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2360
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/705.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 #705
----
commit 8ad138d02201d2b593ebb579b51b0c853829b568
Author: Mark Payne <ma...@hotmail.com>
Date: 2016-07-22T13:21:12Z
NIFI-2360: Leave ZooKeeper running when a node is disconnected. Do not allow the last node in the cluster to be disconnected. Change ClusterProtocoLHeartbeater to use RetryNTime retry strategy instead of RetryForever because web requests could block on this
----
> Improve robustness of cluster when relying on embedded zookeeper
> ----------------------------------------------------------------
>
> Key: NIFI-2360
> URL: https://issues.apache.org/jira/browse/NIFI-2360
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.0.0
>
>
> I have a 3 node cluster running an embedded zookeeper. If 2 nodes disconnect, I no longer have a ZooKeeper quorum. As a result, the third node is also disconnected. If I had more nodes, they would also all be disconnected. As a result, I also cannot then go to the cluster page to re-connect them, since there is no cluster coordinator.
> We should make this more robust, predominantly by not starting & stopping the embedded zookeeper server when a node connects & disconnects from cluster but instead just leave the embedded zookeeper server running, even when the node is disconnected from the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)