Introduce soft-leader election mechanism for cc based on observed cluster state #2238
Assignees
Comments
This was referenced Nov 7, 2024
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 12, 2024
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
muhamadazmy
added a commit
to muhamadazmy/restate
that referenced
this issue
Nov 13, 2024
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
Every
Adminnode 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 theSchedulerand theLogsController).The text was updated successfully, but these errors were encountered: