We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When a pvc both have tidb.pingcap.com/pod-scheduling and tidb.pingcap.com/pvc-defer-deleting, later pods cannot be scheduled:
tidb.pingcap.com/pod-scheduling
tidb.pingcap.com/pvc-defer-deleting
apiVersion: v1 kind: PersistentVolumeClaim metadata: annotations: pv.kubernetes.io/bind-completed: "yes" tidb.pingcap.com/pod-name: stability-cluster1-pd-4 tidb.pingcap.com/pod-scheduling: 2019-04-30T10:39:17Z tidb.pingcap.com/pvc-defer-deleting: 2019-04-30T10:41:56Z
E0430 11:32:36.422566 1 mux.go:107] unable to filter nodes: pods "stability-cluster1-pd-4" not found I0430 11:32:36.427365 1 scheduler.go:75] scheduling pod: stability-cluster2/stability-cluster2-pd-2 I0430 11:32:36.427410 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.156] E0430 11:32:36.822106 1 mux.go:107] unable to filter nodes: pods "stability-cluster2-pd-4" not found I0430 11:32:36.826812 1 scheduler.go:75] scheduling pod: stability-cluster1/stability-cluster1-pd-2 I0430 11:32:36.826833 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.160] E0430 11:32:37.221874 1 mux.go:107] unable to filter nodes: pods "stability-cluster1-pd-4" not found I0430 11:32:37.226280 1 scheduler.go:75] scheduling pod: stability-cluster2/stability-cluster2-pd-2 I0430 11:32:37.226295 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.156] E0430 11:32:37.622519 1 mux.go:107] unable to filter nodes: pods "stability-cluster2-pd-4" not found I0430 11:32:37.627086 1 scheduler.go:75] scheduling pod: stability-cluster1/stability-cluster1-pd-2 I0430 11:32:37.627126 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.160] E0430 11:32:38.021707 1 mux.go:107] unable to filter nodes: pods "stability-cluster1-pd-4" not found I0430 11:32:38.026198 1 scheduler.go:75] scheduling pod: stability-cluster2/stability-cluster2-pd-2 I0430 11:32:38.026219 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.156] E0430 11:32:38.421899 1 mux.go:107] unable to filter nodes: pods "stability-cluster2-pd-4" not found I0430 11:32:38.427214 1 scheduler.go:75] scheduling pod: stability-cluster1/stability-cluster1-pd-2 I0430 11:32:38.427249 1 scheduler.go:78] entering predicate: HighAvailability, nodes: [172.16.4.160] E0430 11:32:38.821963 1 mux.go:107] unable to filter nodes: pods "stability-cluster1-pd-4" not found
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
When a pvc both have
tidb.pingcap.com/pod-scheduling
andtidb.pingcap.com/pvc-defer-deleting
, later pods cannot be scheduled:The text was updated successfully, but these errors were encountered: