[
https://issues.apache.org/jira/browse/NIFI-5096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16444432#comment-16444432
]
ASF GitHub Bot commented on NIFI-5096:
--------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/2646
@markap14 These changes look like they will reduce the time when there are
multiple primaries (leaders) in the event the existing primary isn't notified
of the change. That's definitely an improvement, however, I was curious if you
tried incorporating a `ConnectionStateListener` for the node to be more
proactively notified when the connection is SUSPENDED or LOST. Here's an SO
post [1] where it is discussed.
[1]
https://stackoverflow.com/questions/41042798/how-to-handle-apache-curator-distributed-lock-loss-of-connection
> 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)
