[CURATOR-444] LeaderLatch sends events that leads to simultaneously leadership after blocking zookeeper peer communication

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.12.0, 4.0.0
• Component/s: Recipes
• Environment: Linux
• Assignee: Jordan Zimmerman
• Reporter: Borja Bravo Alférez
• Created: 27/Nov/17 11:13
• Updated: 06/Feb/19 02:34

Description

How to reproduce the error:

• 3 Zookeeper nodes.
• Using LeaderLatch recipe with a listener.
• We block the zookeeper network with the attached script. It blocks communication between zookeepers. Note that comunication is lost only for 10 seconds that is exactly our default session timeout.

Our curator configuration:

• Base sleep 100ms
• Max sleep 5000ms
• Default connection timeout 15000ms
• Default Session timeout 10000ms

I am working with a pull request. Fix seems trivial but creating the test not so much.

Issue Links

• links to: Pull request 243