-
Notifications
You must be signed in to change notification settings - Fork 423
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
[Umbrella] Autoscaler improvements #2600
Comments
/assign @ryanaoleary |
TODO: I'll leave a comment outlining the V2 beta scope and remaining issues to solve for V1 & V2. |
@ryanaoleary thanks! You can compile a list of issues, and we can schedule a meeting to go through them one by one. |
The issues that I think we ought to complete before considering Autoscaler v2 in Beta can be broken down into observability improvements and reliability bug-fixes. Observability:
Reliability:
Several of the completed issues mentioned in the issue description fix the main reliability issues found within the v1 Autoscaler, and from my manual testing with multiple CPU and GPU worker-groups I've seen consistent behavior. Additionally, new features in the v2 autoscaler such as configuring idle node timeouts by node type will enable users with more fine-grained control of their workloads and minimize the amount of autoscaling errors we were previously seeing. We should also consider it a requirement to ensure reliable testing for CPUs, GPUs, and custom accelerators before considering v2 beta. |
Search before asking
Description
TODO:
This umbrella issue covers two topics:
Reliability
Top priority:
Usability
Testing
Observability / Debuggability
Others
ray.io/group
label. ray#48840Use case
No response
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: