kubernetes / kubernetes/kubernetes
Support async moveAllToActiveOrBackoffQueue in scheduler
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 128k
- Forks
- 44.6k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 208
Description
### What would you like to be added?
Kube-Scheduler uses scheduling hint to determine whether the pods should be moved to ActiveQ. Scheduler will lock and traverse all pods in unschedulableQ to find which pods might become schedulable due to the incoming event. Many operation on SchedulingQueue will be blocked if the events come too frequently.
For example, if someone updates assigned pod in a high frequency, the SchedulingQueue will be blocked by assignedPodUpdate() and new pods can not be added into the activeQ, result in scheduler hang.
I want to make moveAllToActiveOrBackoffQueue run in a background goroutine, check multi cluster events once a time, and limit its frequency to avoid influencing other SchedulingQueue operation.
### Why is this needed?
If someone updates assigned pod in a high frequency, the SchedulingQueue will be blocked by assignedPodUpdate() and new pods can not be added into the activeQ, result in scheduler hang.
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
Locate moveAllToActiveOrBackoffQueue and the assignedPodUpdate path in the scheduler's SchedulingQueue implementation. Read how queue locking and scheduling-hint events are handled, then determine batching and frequency behavior for multi-cluster events. Done means frequent assigned-pod updates no longer block adding pods to ActiveQ while affected pods are moved correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100