pingcap / pingcap/tidb-operator
Provide TiDB Operator Disaster Recovery Runbook
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
In automotive today, there is always an automotive supervisor to wait for taking over the car in dangerous scenarios. In the design of TiDB Operator, we also need a takeover mechanism. There are many dangerous scenarios that we need to have a method to take over the cluster. We need an operation manual to cover the most severe scenario. And we need to provide some techniques for this feature request.
Is your feature request related to a problem? Please describe:
Describe the feature you'd like:
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
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 reviewing the TiDB Operator repository's existing operational documentation and Kubernetes disaster-recovery guidance. Done should be a runbook covering the most severe cluster scenarios, takeover procedures, and the techniques needed to apply them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100