Open yx367563 opened 3 months ago
Hi @yx367563, for now please use autoscaler v1. v2 development is pause right now due to limited resource.
@jjyao In fact, I want to use autosclaer v2 simply because there was a problem with killing working nodes in v1(https://github.com/ray-project/ray/issues/46492). I was recommended to try v2 and the bug was indeed eliminated, and would like to ask if there is any solution in v1?
Thanks for reporting @yx367563 . Would it be easy for you to share some head node logs (particularly the monitor logs) with v2?
Sorry, I have stopped using autoscaler v2. I hope this bug can be fixed in v1 (https://github.com/ray-project/ray/issues/46492).
Sorry, I have stopped using autoscaler v2. I hope this bug can be fixed in v1 (ray-project/ray#46492).
Sure - I will see if i have time to repro this on my end. Thanks!
@rickyyx Thank you! And looking forward to receiving your feedback!
Search before asking
KubeRay Component
ray-operator
What happened + What you expected to happen
For the same environment, only changing the use of autoscaler v1 or v2, for a one-time submission of 8000 tasks, v1 can work normally, but v2 will always be stuck, can not be scaled up version: Ray 2.23.0 Kuberay 1.1.1
Reproduction script
Anything else
I want to know what has made recent progress in AutoScaler V2? It seems that it has not been updated for a long time
Are you willing to submit a PR?