Cluster-wide configuration of target voter/standby count
Open
Feature
- Dominant language
- C
- Stars
- 4.4k
- Forks
- 254
- PR merge metrics
- No merged PRs in 30d
Description
As @freeekanayaka suggested in #501 (and #507), we should support a way to configure the target number of voters and standbys for role management such that these parameters are persisted and replicated across the cluster. That is, setting these values should only be allowed on the leader, and it should go through the raft log.
Contributor guide
Research direction
Start by reviewing issues #501 and #507, then trace the role-management configuration and the raft-log path for leader-only changes. Done means the target voter and standby counts can be configured by the leader and are persisted and replicated across the cluster.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100