pingcap / pingcap/tidb-operator
Scaling in TiKV blocked by `not found in cluster` error
Open
@KanShiori is already working on this.
Since Jul 25, 2022.
- 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.3.2
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?
# k -n tidb60441 get pod
NAME READY STATUS RESTARTS AGE
db-discovery-7b5b664f88-wkhgr 1/1 Running 0 3h48m
db-monitor-0 3/3 Running 0 3h48m
db-pd-0 1/1 Running 0 3h48m
db-tidb-0 3/3 Running 0 107m
db-tidb-initializer-b29tn 0/1 Completed 0 3h48m
db-tikv-3 1/1 Running 0 57m
db-tikv-4 1/1 Running 0 57m
db-tikv-5 1/1 Running 0 57m
db-tikv-6 1/1 Running 0 34m
db-tikv-7 1/1 Running 0 34m
db-tikv-8 1/1 Running 0 34m
What did you do?
Scale out 3 new Pods and then scale in 3 Pods very soon
What did you expect to see?
The Pods are scaled in
What did you see instead?
The latest Pod tikv-8 cannot scale in
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.
Assessment
This issue has not been assessed yet.