how to improve high-availability when waitTillLeaderIsReadyOrStepDown
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 110
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
If the leader needs to be really ready, it needs to apply all business data successfully after the election.
During this period of time, the leader cannot actually provide services. In Gringofts, the method waitTillLeaderIsReadyOrStepDown will be waiting.
If a lot of data needs to be applied, it will wait for a long time.
Does Gringofts have some high-availability solutions that can minimize the time when services are unavailable?
Thank you.
Contributor guide
No contributing guide indexed for this repository
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 with waitTillLeaderIsReadyOrStepDown and trace how leader election readiness applies business data before services resume. The issue does not name files or tests; first establish the affected readiness and replication paths, then define and validate an approach that reduces unavailable time while preserving successful data application.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100