kezhuw opened a new pull request, #2208: URL: https://github.com/apache/zookeeper/pull/2208
The rollover procedure: 1. Treats last proposal of an epoch as rollover proposal. 2. Requests from next epoch are proposed normally. 3. Fences next epoch once rollover proposal persisted. 4. Proposals from next epoch will not be written to disk before rollover committed. 5. Leader commits rollover proposal once it get quorum ACKs. 6. Blocked new epoch proposals are logged once rollover proposal is committed in corresponding nodes. This results in: 1. No other lead cloud lead using next epoch number once rollover proposal is considered committed. 2. No proposals from next epoch will be written to disk before rollover proposal is considered committed. Refs: ZOOKEEPER-1277, ZOOKEEPER-2789, ZOOKEEPER-4870, ZOOKEEPER-4882, ZOOKEEPER-4570 and ZOOKEEPER-4571 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@zookeeper.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
