Recovering from missing node
Open
Nobody has claimed this yet.
type/question
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
General Question
Before asking a question, make sure you have:
- ✅ Searched existing Stack Overflow questions.
- ✅ Googled your question.
- ✅ Searched open and closed GitHub issues
- ✅ Read the documentation:
How do I recover from a total node failure? If the node goes down and everything goes missing but TiDB is still up, what is the correct steps to recover that the cluster back to a fully functional state?
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 reviewing the existing TiDB and TiUP documentation referenced in the issue and identify the documented procedure for total node failure while TiDB remains available. Clarify the expected recovery scope and document the steps needed to return the cluster to a fully functional state.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases, distributed-systems
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100