pingcap / pingcap/tidb-operator
Graceful upgrade of TiDB
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
https://docs.pingcap.com/tidb-in-kubernetes/dev/access-tidb#gracefully-upgrade-the-tidb-cluster introduces the prestop hook for TiDB, however, we have to make sure that TiDB may be gracefully upgraded (the long connections will be down but no new connections will be rejected):
- For on-premise deploy, can the ingress controller meet the requirement? How to configure them?
- For public cloud deploy, can the LB + prestop hook meet the requirement?
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
Start with the linked TiDB Operator documentation at the graceful-upgrade section and review the ingress-controller, load-balancer, and preStop-hook behavior described there. Compare the on-premise and public-cloud deployment paths; done means the supported configuration for graceful upgrades is established and documented without rejecting new connections while existing ones drain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- cloud, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100