[CURATOR-518] Curator. LeaderSelector. Two successive calls to interruptLeadership() will break autoRequeue.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.1, 4.2.0
• Fix Version/s: 5.5.0
• Component/s: Recipes
• Labels: newbie
• Environment: Windows 8, JRE 1.8.0_181
• External issue URL: https://bitbucket.org/tibonarium/zookeeper-interrupt-leadership-java/src/master/
• Assignee: Kezhu Wang
• Reporter: Bulatov Oleg
• Created: 15/Apr/19 09:39
• Updated: 17/May/23 15:48
• Resolved: 19/Apr/23 20:47

Description

Curator. LeaderSelector. Two successive calls to interruptLeadership() will break autoRequeue

If we set autoRequeue to TRUE. But during execution interruptLeadership() will be called from another thread before internalRequeue() completed its work. Then it will break recursive call to internalRequeue(), so that client will not ask for leadership and get stuck.

We can solve this problem if we check hasLeadership() before calling interruptLeadership(). But it is strange that such check curator library does not do internally.

Issue Links

• causes: CURATOR-671 TestLeaderSelectorCluster.testLostRestart failed three runs