Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix a bug that can deadlock a newly elected leader #8

Closed
a3y3 opened this issue Jun 26, 2022 · 0 comments
Closed

Fix a bug that can deadlock a newly elected leader #8

a3y3 opened this issue Jun 26, 2022 · 0 comments

Comments

@a3y3
Copy link
Owner

a3y3 commented Jun 26, 2022 •
edited
Loading

When the old leader is partitioned off (or crashes), the newly elected leader can have values surfaced on applyCh - but this can cause a problem since no RPC is waiting to consume them (the old leader's RPC already did that).
Thus, every leader also needs to verify if someone is even expecting that value before going into a wait.
@a3y3 a3y3 moved this from Todo to In Progress in PegasusDB Project Jun 26, 2022
@a3y3 a3y3 changed the title Fix a bug that's causing no progress to happen in a partitioned leader Fix a bug that can deadlock a new leader Jun 26, 2022
@a3y3 a3y3 changed the title Fix a bug that can deadlock a new leader Fix a bug that can deadlock a newly elected leader Jun 26, 2022
a3y3 added a commit that referenced this issue Jun 26, 2022
@a3y3
Fix a bug that can deadlock a newly elected leader (#8)
394ae28
@a3y3 a3y3 closed this as completed Jun 27, 2022
Repository owner moved this from In Progress to Done in PegasusDB Project Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
PegasusDB Project
Status: Done
Milestone
No milestone
Development

No branches or pull requests
1 participant
@a3y3