You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Mohammad Arshad (Jira)" <ji...@apache.org> on 2021/03/29 10:24:00 UTC

[jira] [Created] (ZOOKEEPER-4269) acceptedEpoch.tmp rename failure will cause server startup error

Mohammad Arshad created ZOOKEEPER-4269:
------------------------------------------

             Summary: acceptedEpoch.tmp rename failure will cause server startup error
                 Key: ZOOKEEPER-4269
                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4269
             Project: ZooKeeper
          Issue Type: Bug
            Reporter: Mohammad Arshad
            Assignee: Mohammad Arshad


accepted epoch is first written to temporary file acceptedEpoch.tmp then this file is renamed to acceptedEpoch.


Failure, either because of exception or power-off, in renaming the acceptedEpoch.tmp file will cause server startup error with message "The current epoch, x, is older than the last zxid y"

To handle this scenario we should read accepted epoch from this temp file as well.

For more context, refer https://github.com/apache/zookeeper/pull/1109

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)