You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar feature requirement.
Description
#2663 adds a new field suspend for each worker group. Ray Autoscaler should not submit any scale requests for worker groups which have already been suspended.
Use case
No response
Related issues
No response
Are you willing to submit a PR?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered:
Resolvesray-project/kuberay#2666.
ray-project/kuberay#2663 adds a new `suspend` field to the
KubeRay worker group spec for suspending worker groups. A suspended worker group should
be scaled to 0 and never be scaled up until the group is resumed.
Since there is no similar functionality in the `available_node_types` definition,
the best way to let the autoscaler know a worker group has been suspended is to
set its max_workers to 0 as well as its min_workers.
This PR makes the KubeRay autoscaling config producer produce a config with
both max_workers and min_workers set to 0 if the worker group has been suspended.
The autoscaler will periodically take the config and do its work.
Signed-off-by: Rueian <[email protected]>
Search before asking
Description
#2663 adds a new field
suspend
for each worker group. Ray Autoscaler should not submit any scale requests for worker groups which have already been suspended.Use case
No response
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: