[
https://issues.apache.org/jira/browse/ZOOKEEPER-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121026#comment-13121026
]
[email protected] commented on ZOOKEEPER-1209:
----------------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2213/
-----------------------------------------------------------
Review request for zookeeper and Mahadev Konar.
Summary
-------
The attached patch handles Syncconnected, Disconnected, Expired connection
events. Tries to make client to neutral after disconnection and stop after
session expiration, rather than in Active mode.
This addresses bug ZOOKEEPER-1209.
https://issues.apache.org/jira/browse/ZOOKEEPER-1209
Diffs
-----
./src/recipes/election/test/org/apache/zookeeper/recipes/leader/LeaderElectionAwareTest.java
PRE-CREATION
./src/recipes/election/src/java/org/apache/zookeeper/recipes/leader/LeaderElectionSupport.java
1179108
Diff: https://reviews.apache.org/r/2213/diff
Testing
-------
See test program and description on
https://issues.apache.org/jira/browse/ZOOKEEPER-1209
Thanks,
Rakesh
> LeaderElection recipe doesn't handle the split-brain issue, n/w disconnection
> can bring both the client nodes to be in ELECTED
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1209
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1209
> Project: ZooKeeper
> Issue Type: Bug
> Components: recipes
> Affects Versions: 3.3.3
> Reporter: Rakesh R
> Assignee: Rakesh R
> Attachments: ZOOKEEPER-1209.patch
>
>
> *Case1-* N/w disconnection can bring both the client nodes to be in ELECTED
> state. Current LeaderElectionSupport(LES) f/w handles only 'NodeDeletion'.
>
> Consider the scenario where ELECTED and READY nodes are running. Say ELECTED
> node's n/w got failed and is "Disconnected" from ZooKeeper. But it will
> behave as ELECTED as it is not getting any events from the
> LeaderElectionSupport(LES) framework.
> After sessiontimeout, node in READY state will be notified by 'NodeDeleted'
> event and will go to ELECTED state.
> *Problem:*
> Both the node becomes ELECTED and finally the user sees two Master (ELECTED)
> node and cause inconsistencies.
> *Case2-* Also in this case, Let's say if user has started only one client
> node and becomes ELECTED. After sometime n/w has disconnected with the
> ZooKeeper server and the session got expired.
> *Problem:*
> Still the client node will be in the ELECTED state. After sometime if user
> has started the second client node. Again both the nodes becomes ELECTED.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
