raft: consider live-update of election and heartbeat tick for raft nodes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
#668 included two flags to configure the heartbeat and election tick at bootstrap time. Those are fixed at bootstrap and can be updated by restarting the process with new values for those flags but nothing prevents updating the node without stopping the process.
This would involve stopping all the components in the Manager and then restart Raft with a new Config from the submitted Spec. This comes with a few implications though as this can be a risky operation. Mainly because we would have to coordinate nodes during the restart process in order not to lose a quorum of nodes and keep the cluster running. Also because those parameters can be mistakenly updated in the Spec thus triggering the node restart process, which is not a safe operation.
Related to #650
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issues #668 and #650, then trace how the Manager and Raft use the submitted Spec and Config during bootstrap. The issue describes coordinating a live restart without losing quorum, but it does not define an implementation scope or concrete completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100