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
---
