Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Dynamically reclaiming resources #756
Dynamically reclaiming resources #756
Changes from all commits
d4de946
fab9584
60871b0
d894851
3720ecd
1d57739
cf30176
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I'm having second thoughts here.
If we assume that the admission section can be modified after admission (to update Count and usage), then I prefer we have
reclaimableCount
inside the admission struct.I think this might be a better idea as we move towards elastic jobs. @tenzen-y ?
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.
Does this mean we have
reclaimableCount
inside the admission instead of having thisReclaimablePods
(removingReclaimablePods
)?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.
yes, that's what I'm thinking.
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.
IIRC, we selected
ReclaimablePods
instead ofreclaimableCount
since it could be misleading when the job is suspended.#742 (comment)
However, as @alculquicondor says, we can ignore that concern if we have
reclaimableCount
inside theAdmission
.right. The
Admission
has thereclaimableCount
would be more natural for the elastic job.@trasc Are you concerned about having
reclaimableCount
inside theAdmission
?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.
The admission is not changed when reclaimable changes.
SSA conflicts. We should keep them separated.
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.
Let's say we have elastic jobs. Then the kueue scheduler+preemption could update
count
.However, this is generally independent from the concept of reclaiming pods.
Ok, let's keep it like this.
Any reason why not make this
map[string]int32
?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.
just to look similar to flavors and usage
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.