[
https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15381016#comment-15381016
]
ASF GitHub Bot commented on NIFI-2289:
--------------------------------------
GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/665
NIFI-2289: Directly ask ZooKeeper which node is cluster coordinator a…
…nd add watches on the ZNode rather than relying on Node Status Updates
over the cluster protocol because cluster protocol may get the events
out-of-order
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2289
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/665.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 #665
----
commit c500d7e97aed276a18f17ae6a00e73bf5ad0665f
Author: Mark Payne <[email protected]>
Date: 2016-07-17T01:19:44Z
NIFI-2289: Directly ask ZooKeeper which node is cluster coordinator and add
watches on the ZNode rather than relying on Node Status Updates over the
cluster protocol because cluster protocol may get the events out-of-order
----
> Cluster sometimes gets into state where it always says 'no Cluster
> Coordinator elected'
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-2289
> URL: https://issues.apache.org/jira/browse/NIFI-2289
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Critical
> Fix For: 1.0.0
>
>
> When running in clustered mode, occasionally NiFi will get into a state where
> it indicates for each request that no cluster coordinator exists, even though
> one is clearly elected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
