[ 
https://issues.apache.org/jira/browse/NIFI-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386733#comment-15386733
 ] 

ASF subversion and git services commented on NIFI-2289:
-------------------------------------------------------

Commit 7f2bda29d968694f62c7e776839efb448215f6f9 in nifi's branch 
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=7f2bda2 ]

NIFI-2289: Ensure that we include Node ID's of all nodes when finding cluster 
coordinator, even if the node is currently still connecting or has not yet 
joined the cluster, which ccan be the case if all nodes in the cluster are 
restarting at the same time.

This closes #681

Signed-off-by: jpercivall <[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)

Reply via email to