Skip to content

[core][autoscaler] Don't error if rayStartParams absent #51954

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

Merged
merged 1 commit into from
Apr 3, 2025

Conversation

davidxia
Copy link
Contributor

@davidxia davidxia commented Apr 3, 2025

We are planning on making rayStartParams optional
and not present in the RayCluster K8s custom resource output
if it's empty. ray-project/kuberay#3202

We need to make its autoscaler code not error when it's absent.
This change is also needed for the integration tests in that PR to pass.

Signed-off-by: David Xia david@davidxia.com

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

@davidxia davidxia marked this pull request as ready for review April 3, 2025 12:58
@jcotant1 jcotant1 added the core Issues that should be addressed in Ray Core label Apr 3, 2025
We are planning on making `rayStartParams` optional
and not present in the RayCluster K8s custom resource output
if it's empty. ray-project/kuberay#3202

We need to make its autoscaler code not error when it's absent.
This change is also needed for the integration tests in that PR to pass.

Signed-off-by: David Xia <david@davidxia.com>
@kevin85421
Copy link
Member

cc @rueian would you mind reviewing this PR? Thanks!

@kevin85421 kevin85421 self-assigned this Apr 3, 2025
Copy link
Contributor

@rueian rueian left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kevin85421 kevin85421 added the go add ONLY when ready to merge, run all tests label Apr 3, 2025
@kevin85421
Copy link
Member

@davidxia please ping me when all CI pass! Thanks!

@jjyao jjyao changed the title [core][autoscaler] don't error if rayStartParams absent [core][autoscaler] Don't error if rayStartParams absent Apr 3, 2025
@jjyao jjyao merged commit 4190c40 into ray-project:master Apr 3, 2025
6 checks passed
@davidxia davidxia deleted the rsp branch April 4, 2025 11:45
davidxia added a commit to davidxia/kuberay that referenced this pull request May 9, 2025
in `ray-operator/test/e2erayservice/rayservice_ha_test.go`'s
`TestRayServiceZeroDowntimeUpgrade` and `TestAutoscalingRayService`.

They currently fail because the autoscaler is using Ray 2.41.0 and doesn't have
this patch. ray-project/ray#51954

We will revert this commit after Ray is upgraded in this repo to 2.45.0 or
above in PRs like ray-project#3547.

Signed-off-by: David Xia <david@davidxia.com>
davidxia added a commit to davidxia/kuberay that referenced this pull request May 10, 2025
* `RayClusters` with `rayStartParams: {}` will continue to be serialized with
  the empty map.
* `RayClusters` without `rayStartParams` will be serialized without the field.

This prevents a backwards-incompatible change with RayClusters that use the
autoscaler with Ray versions earlier than 2.45.0 which lack this change
ray-project/ray#51954.

Signed-off-by: David Xia <david@davidxia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-backlog core Issues that should be addressed in Ray Core go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants