[CURATOR-724] LeaderLatch isn't able to recover after zk recover/leaderPath missing.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.5.0, 5.6.0, 5.7.0, 5.7.1
• Fix Version/s: 5.8.0
• Component/s: Recipes
• Assignee: Zili Chen
• Reporter: Kuradeon
• Created: 21/Nov/24 06:23
• Updated: 21/Dec/24 20:30
• Resolved: 21/Dec/24 20:30

Description

zk server: 3.7.2

After https://github.com/apache/curator/pull/430, after the zk was down and recovered, the LeaderLatch called getChildren() instead of reset() to recover the leader election. But getChildren() triggers setNode() via callback client.getChildren().inBackground(callback).forPath(ZKPaths.makePath(latchPath, null)). If the leaderPath node doesn't exist after zk recovered, then the LeaderLatch node wouldn't never recreated.

There is a temporary solution, adding a ConnectionStateListener before the LeaderLatch internal ConnectionStateListener, to create the leaderPath node manually. Then this issue will be fixed.

Issue Links

• links to: GitHub Pull Request #515