[
https://issues.apache.org/jira/browse/ZOOKEEPER-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229937#comment-13229937
]
Hadoop QA commented on ZOOKEEPER-1277:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12518426/ZOOKEEPER-1277_trunk.patch
against trunk revision 1297740.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 5 new or modified tests.
+1 javadoc. The javadoc tool did not generate any 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 1.3.9)
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/994//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/994//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/994//console
This message is automatically generated.
> servers stop serving when lower 32bits of zxid roll over
> --------------------------------------------------------
>
> Key: ZOOKEEPER-1277
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1277
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.3
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Priority: Critical
> Fix For: 3.3.5, 3.4.4, 3.5.0
>
> Attachments: ZOOKEEPER-1277_br33.patch, ZOOKEEPER-1277_br33.patch,
> ZOOKEEPER-1277_br33.patch, ZOOKEEPER-1277_br33.patch,
> ZOOKEEPER-1277_br34.patch, ZOOKEEPER-1277_br34.patch,
> ZOOKEEPER-1277_trunk.patch, ZOOKEEPER-1277_trunk.patch
>
>
> When the lower 32bits of a zxid "roll over" (zxid is a 64 bit number, however
> the upper 32 are considered the epoch number) the epoch number (upper 32
> bits) are incremented and the lower 32 start at 0 again.
> This should work fine, however in the current 3.3 branch the followers see
> this as a NEWLEADER message, which it's not, and effectively stop serving
> clients. Attached clients seem to eventually time out given that heartbeats
> (or any operation) are no longer processed. The follower doesn't recover from
> this.
> I've tested this out on 3.3 branch and confirmed this problem, however I
> haven't tried it on 3.4/3.5. It may not happen on the newer branches due to
> ZOOKEEPER-335, however there is certainly an issue with updating the
> "acceptedEpoch" files contained in the datadir. (I'll enter a separate jira
> for that)
--
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
