Re: [I] [CURATOR-54] No reliable way to cancel leadership in LeaderSelector when connection fails due to edge cases [curator]

["jira-importer (via GitHub)" <gi...@apache.org>]

jira-importer commented on issue #575:
URL: https://github.com/apache/curator/issues/575#issuecomment-2604699145

   <i><a href="https://issues.apache.org/jira/secure/ViewProfile.jspa?name=randgalt">randgalt</a>:</i>
   <p> It was not possible to correctly handle connection state issues with the LeaderSelectorListener. There was an edge case where if<br/>
       the connection was lost before takeLeadership() was called, the thread would not be known and the existing sample code on<br/>
       how to handle stateChanged would not work.</p>
   
   <p>    Introduced CancelLeadershipException to signal to the LeaderSelector instance that it should cancel the leadership. Also<br/>
       added a direct method of canceling leadership.</p>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@curator.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org