[
https://issues.apache.org/jira/browse/NIFI-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444454#comment-16444454
]
ASF GitHub Bot commented on NIFI-5096:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2646
@markap14 Looks like our `LeaderSelectionListener` does implement
`ConnectionStateListener`. Do we need to update code on our side to explicitly
give up leadership in the SUSPENDED or LOST scenarios?
> 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
>
> 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)
