-
Notifications
You must be signed in to change notification settings - Fork 52
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
Priority-based exclusive placement #687
Conversation
✅ Deploy Preview for kubernetes-sigs-jobset canceled.
|
d0d1a75
to
b279a60
Compare
b279a60
to
fe31bec
Compare
By limiting exclusive placement to jobs within the same priority level, couldn't this cause partial scheduling of jobs with different priority levels onto the same TPU slice? |
On the same slice, only one workload should be running, the assumption is that this workload will occupy all resources on that slice. If a race happens, then the higher priority slice will eventually preempt the lower priority one. We should move to a proper API for exclusive placement in the next release, and have this configured as a knob, call it |
@danielvegamyhre the test is failing due to golang version, I updated it in kubernetes/test-infra#33689, can you please take a look? |
Done |
fe31bec
to
77c86ea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, just one minor comment
Co-authored-by: Daniel Vega-Myhre <105610547+danielvegamyhre@users.noreply.github.com>
done, thanks |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahg-g, danielvegamyhre The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/kind feature
What this PR does / why we need it:
Limit exclusive placement to the same priority level.
Which issue(s) this PR fixes:
Fixes ##682
Special notes for your reviewer:
Does this PR introduce a user-facing change?