-
Notifications
You must be signed in to change notification settings - Fork 501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scheduler cannot schedule TiKV #602
Comments
|
kubectl describe po -n tidb21 demo-tikv-2
|
kubectl get pvc -n tidb21
|
kubectl get pv
|
The tikv-2 PVC was bound, but can't scheduled, and there are no
|
As per #468 this blocks a new cluster from being scheduled. The tidb-scheduler logs are listed above. kube-scheduler looks the same.
|
Is the unscheduled pod retried by the scheduler repeatedly? If the scheduler retries scheduling the pod but always fail, it is unrelated to the issue we found in IDC k8s env. In IDC k8s env, the tidb-scheduler didn't try to schedule the new TikV pods. |
Yes, it keeps trying to schedule. |
@cofyc suggests:
or uprade to v1.14+ @gregwebs can you have a try? |
I filled out a form to be an alpha user of 1.14 on GKE. I am still waiting... tidb-operator is using kube-scheduler v1.13.6 which matches the GKE version when it was installed. |
I cannot reproduce this anymore |
Bug Report
The scheduler continually logs:
The kube-scheduler log is similar.
There are no events for tikv-2 when it is described.
I got to this state after creating a tidb cluster, then creating a 2nd tidb cluster and deleting the first cluster. I deleted Released PV.
The text was updated successfully, but these errors were encountered: