Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

ZOOKEEPER-4883: Rollover leader epoch when zxid counter is exhausted #2208

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
kezhuw wants to merge 1 commit into apache:master
base: master
Choose a base branch
Loading
from kezhuw:zxid-rollover

Conversation

Copy link
Member

@kezhuw kezhuw commented Oct 28, 2024
edited
Loading

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

zhaohaidao reacted with thumbs up emoji
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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

AltStyle によって変換されたページ (->オリジナル) /