Soft-leader election mechanism for cc based on observed cluster state #2252
+59
−13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Nov 8, 2024
muhamadazmy
force-pushed
the
pr2252
branch
5 times, most recently
from
500249c
to
0369a6c
Compare
Summary: Every Admin node runs a CC which can act as the leader. The acting leader is decided based on deterministically sorting all admin nodes (e.g. based on their plain node id) and picking the first alive node. The acting leader is allowed to make control decisions (e.g. calling into the Scheduler and the LogsController). Fixes restatedev#2238
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Soft-leader election mechanism for cc based on observed cluster state
Summary:
Every Admin node runs a CC which can act as the leader. The acting leader is decided based on deterministically sorting all admin nodes
(e.g. based on their plain node id) and picking the first alive node.
The acting leader is allowed to make control decisions (e.g. calling into the Scheduler and the LogsController).
Fixes #2238