[ https://issues.apache.org/jira/browse/ZOOKEEPER-4269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mohammad Arshad updated ZOOKEEPER-4269: --------------------------------------- Fix Version/s: 3.7.1 3.8.0 3.6.3 > 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 > Priority: Major > Labels: pull-request-available > Fix For: 3.6.3, 3.8.0, 3.7.1 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)