[
https://issues.apache.org/jira/browse/NIFI-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446349#comment-16446349
]
ASF subversion and git services commented on NIFI-5096:
-------------------------------------------------------
Commit 54eb6bc23211ad2b499f42e14759f3646f806d2f in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=54eb6bc ]
NIFI-5096: Periodically poll ZooKeeper to determine the leader for each
registered role in Leader Election. This avoids a condition whereby a node may
occasionally fail to receive notification that it is no longer the elected
leader.
NIFI-5096: More proactively setting leadership to false when ZooKeeper/Curator
ConnectionState changes
This closes #2646
> When Primary Node changes, occasionally both the new and old primary nodes
> continue running processors
> ------------------------------------------------------------------------------------------------------
>
> Key: NIFI-5096
> URL: https://issues.apache.org/jira/browse/NIFI-5096
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.7.0
>
>
> Occasionally we will see that Node A is Primary Node and then the Primary
> Node switches to Node B, resulting in both Node A and Node B running
> processors that are marked as Primary Node only.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)