Github user egor-ryashin commented on the issue:
https://github.com/apache/curator/pull/243
We've got continuous issues with that bug (two critical nodes becoming
leaders simultaneously begin to damage the work of each other), and I would
like this work to be continued, though I see it lost attention some time ago.
Right now I'm looking at the code trying to figure out where exactly it's
broken and I found this line quite strange
https://github.com/apache/curator/pull/243/files#diff-edf135a1ae8f33bd78d8371b25f2d5a6R544
IE, we got 3 children:
> 0
> 1
> 2
And **ourIndex** = 2, why would we add a watcher for the child 1?
> sortedChildren.get(ourIndex - 1)
---
