SDK continue writing after one chunkserver dead
Open
new feature
- Dominant language
- C++
- Stars
- 2.8k
- Forks
- 551
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the SDK write path and its handling of a failed chunkserver. Determine how a single chunkserver failure currently affects an ongoing write, then add coverage showing that writing continues after one chunkserver dies and verify the existing SDK tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100