Leader yield if any IO or disk down errors
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 29
- Forks
- 30
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
From @yamingk One issue I see is: when SM experienced disk down, if it happens on leader, HomeStore should yield leadership immediately, the reason is, if we rely on CM to do that, there needs to be some manual ops to kicks in or even if it is automated from CM layer, it also takes some time for CM to detect that. If Homestore can yield leadership it to other member, the other two copies can serve traffic immeidately without any SOPs need to be taken in production.
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 source file, test, or entry point is named. Start by locating HomeStore's handling of leader state and SM disk or IO errors, then inspect how CM-triggered leadership changes are represented. Done means a leader yields promptly after the relevant failure so the other copies can serve traffic without manual production operations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100