[ https://issues.apache.org/jira/browse/ZOOKEEPER-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15343035#comment-15343035 ]
Hadoop QA commented on ZOOKEEPER-1209: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12497779/ZOOKEEPER-1209.patch against trunk revision 1748630. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. -1 javac. The patch appears to cause tar ant target to fail. +1 findbugs. The patch does not introduce any new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3230//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3230//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3230//console This message is automatically generated. > 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 > Fix For: 3.6.0, 3.5.3 > > 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 was sent by Atlassian JIRA (v6.3.4#6332)