[
https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15382333#comment-15382333
]
ASF subversion and git services commented on NIFI-2289:
-------------------------------------------------------
Commit 5c8636edf4bd8ee32892440794e9b40bd009abb6 in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=5c8636e ]
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
This closes #665.
Signed-off-by: Bryan Bende <[email protected]>
> 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)
