-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
[autoscaler] Fix semantics of request_resources #11820
Conversation
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.
Left a few comments, please take a look.
Please remember to add the author action required label! |
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.
See my two comments.
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.
@AmeerHajAli I think you're misunderstanding the logic; the nodes to add based on requests is a subset of nodes to add. It's already included due to this line:
101: resource_demands += resource_requests
LGTM. |
Why are these changes needed?
The semantics of request_resources was broken in the multi node autoscaler, since we did not take into account existing resource usage.
Related issue number
Closes #11417
Closes #10836