You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Patrick Hunt (Resolved) (JIRA)" <ji...@apache.org> on 2012/03/23 01:36:23 UTC
[jira] [Resolved] (ZOOKEEPER-1278) acceptedEpoch not handling zxid
rollover in lower 32bits
[ https://issues.apache.org/jira/browse/ZOOKEEPER-1278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt resolved ZOOKEEPER-1278.
-------------------------------------
Resolution: Duplicate
Fix Version/s: (was: 3.5.0)
This turns out to be a duplicate of ZOOKEEPER-1277 - that patch causes the leader to be re-elected just prior to rollover. 1277 was applied to 3.3/3.4/3.5(trunk)
> acceptedEpoch not handling zxid rollover in lower 32bits
> --------------------------------------------------------
>
> Key: ZOOKEEPER-1278
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1278
> Project: ZooKeeper
> Issue Type: Bug
> Components: server
> Affects Versions: 3.4.0, 3.5.0
> Reporter: Patrick Hunt
> Assignee: Patrick Hunt
> Priority: Blocker
> Attachments: ZOOKEEPER-1278_br34.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, afaict, in the current 3.4/3.5 the acceptedEpoch/currentEpoch files are not being updated for this case.
> See ZOOKEEPER-335 for changes from 3.3 branch.
--
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