gocrane / crane-scheduler

Crane scheduler is a Kubernetes scheduler which can schedule pod based on actual node load.
Apache License 2.0
224 stars 62 forks source link

replace the k8s scheduler with crane scheduler,new pod pending #5

Closed Tendrun101 closed 1 year ago

Tendrun101 commented 2 years ago

I replace the k8s scheduler with crane scheduler, and then created a new pod. I found the new pod always “Pending”, also no related events info.

... ... QoS Class: Burstable Node-Selectors: Tolerations: node-role.kubernetes.io/master:NoSchedule
node.kubernetes.io/disk-pressure:NoSchedule op=Exists
node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists node.kubernetes.io/pid-pressure:NoSchedule op=Exists node.kubernetes.io/unreachable:NoExecute op=Exists node.kubernetes.io/unschedulable:NoSchedule op=Exists Events:

I can only found some useful info in logs, as as follows: I0614 02:18:42.492977 1 eventhandlers.go:118] "Add event for unscheduled pod" pod="kube-system/kubernetes-dashboard-jqhhq"

I wonder if the new pod is pop from the ‘SchedulingQueue’, and how I solved the problem

autumn0207 commented 2 years ago

I replace the k8s scheduler with crane scheduler, and then created a new pod. I found the new pod always “Pending”, also no related events info.

... ... QoS Class: Burstable Node-Selectors: Tolerations: node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/disk-pressure:NoSchedule op=Exists node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists node.kubernetes.io/pid-pressure:NoSchedule op=Exists node.kubernetes.io/unreachable:NoExecute op=Exists node.kubernetes.io/unschedulable:NoSchedule op=Exists Events:

I can only found some useful info in logs, as as follows: I0614 02:18:42.492977 1 eventhandlers.go:118] "Add event for unscheduled pod" pod="kube-system/kubernetes-dashboard-jqhhq"

I wonder if the new pod is pop from the ‘SchedulingQueue’, and how I solved the problem

which version of k8s are you using?

Tendrun101 commented 2 years ago

I replace the k8s scheduler with crane scheduler, and then created a new pod. I found the new pod always “Pending”, also no related events info. ... ... QoS Class: Burstable Node-Selectors: Tolerations: node-role.kubernetes.io/master:NoSchedule node.kubernetes.io/disk-pressure:NoSchedule op=Exists node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists node.kubernetes.io/pid-pressure:NoSchedule op=Exists node.kubernetes.io/unreachable:NoExecute op=Exists node.kubernetes.io/unschedulable:NoSchedule op=Exists Events: I can only found some useful info in logs, as as follows: I0614 02:18:42.492977 1 eventhandlers.go:118] "Add event for unscheduled pod" pod="kube-system/kubernetes-dashboard-jqhhq" I wonder if the new pod is pop from the ‘SchedulingQueue’, and how I solved the problem

which version of k8s are you using?

v1.20.12

xieydd commented 1 year ago

If needed, i will reopen the issue.