Handle the case the a follower's log was rolled back.
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 110
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Currently, when a follower's log is rolled back, the leader will crash again and again, which leads to no stable leader.
We plan to fix the issue. The expected behavior is:
- The cluster runs as normal. There is a stable leader.
- Leader will send log entries to the follower once its data is recovered.
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
No files, tests, or entry points are named. Start by locating the leader/follower log replication and rollback recovery handling, then reproduce the rollback scenario and verify that the cluster retains a stable leader and the leader resends entries after the follower recovers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100