-
Notifications
You must be signed in to change notification settings - Fork 993
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
multi goroutine deal taskUnschedulable #3921
base: master
Are you sure you want to change the base?
multi goroutine deal taskUnschedulable #3921
Conversation
Welcome @lishangyuzi! |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/assign @lowang-bh |
Have you increase the QPS of kubeclient in volcano scheduler? |
default qps of kubeclient has already met my expectations.It takes approximately 200 seconds for a job with 5000 pods to complete this stage. volcano/cmd/scheduler/app/options/options.go Lines 127 to 128 in b169623
volcano/cmd/scheduler/app/options/options.go Lines 40 to 41 in b169623
The parameters related to my API server QPS are as follows: --max-mutating-requests-inflight=4000
--max-requests-inflight=2000
--watch-cache-sizes=node#2000,pod#10000 |
In the scenario of scheduling large-scale jobs, I also encountered a problem. When the job fails to be scheduled, all the pods under this job will update the PodCondition. Since it is necessary to communicate with the apiserver, this will take a long time.Could we consider using the multi-goroutine approach to handle this part of the logic?