Skip to content

Conversation

kezhuw
Copy link
Member

@kezhuw kezhuw commented Oct 28, 2024

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 leader 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

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 leader 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant