oxidecomputer / oxidecomputer/omicron
Restore decommissioning cockroach nodes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
In #8445 we discovered cases where our current "is it safe to decommission a cockroach node" checks are not sufficient. For now, #8446 disables decommissioning altogether.
This issue tracks that we need to investigate how to know when it's okay to decommission a node, implement that in the cockroach-admin server, and restore decommissioning of expunged nodes.
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
Start by reading issues #8445 and #8446 to understand the unsafe cases and why decommissioning was disabled. Then inspect the cockroach-admin server entry points for the existing decommissioning checks. Done means a reliable safety determination is implemented and decommissioning of expunged nodes is restored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100