pingcap / pingcap/tidb-operator
TidbInitializer pod status stuck at Init 0/1
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
kubectl get po -n tidb-cluster
NAME READY STATUS RESTARTS AGE
basic-discovery-785f8dc869-btq9j 1/1 Running 0 89m
basic-monitor-0 3/3 Running 0 55m
basic-pd-0 1/1 Running 0 89m
basic-pump-0 1/1 Running 0 88m
basic-ticdc-0 1/1 Running 0 88m
basic-tidb-0 1/2 Running 0 88m
basic-tidb-1 1/2 Running 0 82m
basic-tidb-initializer-wzgqn 0/1 Init:0/1 0 13m
basic-tiflash-0 4/4 Running 0 89m
basic-tikv-0 1/1 Running 0 88m
kubectl logs -f basic-tidb-initializer-wzgqn -n tidb-cluster
Error from server (BadRequest): container "mysql-client" in pod "basic-tidb-initializer-wzgqn" is waiting to start: PodInitializing
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
Reproduce the stuck TidbInitializer pod with the shown kubectl get po output, then inspect the initializer's mysql-client container state and the PodInitializing logs. Identify why initialization does not progress and verify that the pod reaches Ready without leaving the TiDB cluster in the reported state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- databases, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100