quickwit-oss / quickwit-oss/quickwit
Add a maintenance operation to identify and remove leaking shards
Open
Nobody has claimed this yet.
bug
low-priority
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
If both a leader and a follower leave the cluster indefinitely, we do not have a mechanism to clean their associated shard.
This is a "recovery" operation in a sense. Forcing it to be a manual operation is not a bad idea, but we should have something for that.
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
No files, tests, or entry points are named. Start by tracing how cluster membership, leaders, followers, and shard cleanup are represented, then review existing recovery or maintenance operations. Done means there is a defined operation that can identify shards whose leader and follower have both left indefinitely and remove them safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100