pingcap / pingcap/tidb-operator
PD scales out unexpectedly
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
v1.1.9
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
asts not enabled.
Deploy a TiDB cluster with 3 PDs, after the cluster is ready, run the following command:
kubectl annotate tc $name pd.tidb.pingcap.com/delete-slots="[0]"
What did you expect to see?
Nothing happens.
What did you see instead?
pd-3 is created.
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
The issue names no source files or tests. Start by reproducing the kubectl annotation against a three-PD TiDB cluster, then trace the TiDB Operator reconciliation handling for pd.tidb.pingcap.com/delete-slots; done means deleting slot 0 does not cause an additional PD pod to be created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100