[ https://issues.apache.org/jira/browse/ZOOKEEPER-2307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15003689#comment-15003689 ]
Hadoop QA commented on ZOOKEEPER-2307: -------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12772143/ZOOKEEPER-2307-03.patch against trunk revision 1713774. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 8 new or modified tests. -1 javadoc. The javadoc tool appears to have generated 1 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +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 passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2956//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2956//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2956//console This message is automatically generated. > ZooKeeper not starting because acceptedEpoch is less than the currentEpoch > -------------------------------------------------------------------------- > > Key: ZOOKEEPER-2307 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2307 > Project: ZooKeeper > Issue Type: Bug > Components: server > Reporter: Arshad Mohammad > Assignee: Arshad Mohammad > Priority: Critical > Fix For: 3.5.2 > > Attachments: ZOOKEEPER-2307-01.patch, ZOOKEEPER-2307-02.patch, > ZOOKEEPER-2307-03.patch > > > This issue occurred in one of our test environment where disk was being > changed to read only very frequently. > The the scenario is as follows: > # Configure three node ZooKeeper cluster, lets say nodes are A, B and C > # Start A and B. Both A and B start successfully, quorum is running. > # Start C, because of IO error C fails to update acceptedEpoch file. But C > also starts successfully, joins the quorum as follower > # Stop C > # Start C, bellow exception with message "The accepted epoch, 0 is less than > the current epoch, 1" is thrown > {code} > 2015-10-29 16:52:32,942 [myid:3] - ERROR [main:QuorumPeer@784] - Unable to > load database on disk > java.io.IOException: The accepted epoch, 0 is less than the current epoch, 1 > at > org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781) > at > org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88) > 2015-10-29 16:52:32,946 [myid:3] - ERROR [main:QuorumPeerMain@111] - > Unexpected exception, exiting abnormally > java.lang.RuntimeException: Unable to run quorum server > at > org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:785) > at > org.apache.zookeeper.server.quorum.QuorumPeer.start(QuorumPeer.java:720) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.runFromConfig(QuorumPeerMain.java:202) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:139) > at > org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:88) > Caused by: java.io.IOException: The accepted epoch, 0 is less than the > current epoch, 1 > at > org.apache.zookeeper.server.quorum.QuorumPeer.loadDataBase(QuorumPeer.java:781) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)