Skip to content
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

RayService: Omits Min and Max replicas from hash calculation #2172

Merged

Conversation

kpitzen
Copy link
Contributor

@kpitzen kpitzen commented May 29, 2024

Why are these changes needed?

Currently, when updating RayService config, changing MinReplicas or MaxReplicas in the autoscaling config triggers an entirely new RayCluster to be instantiated. In order to facilitate orchestrating canary deployments, we'd like to have the ability to scale those parameters on an existing cluster as we move traffic over.

Related issue number

Currently no issue linked, but I can create one if needed.

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

@kousun12
Copy link

would love to see this in the next release

@kpitzen kpitzen force-pushed the KP/RayServiceAutoscalingNoReplacement branch from 5e1d9e9 to 1918c4e Compare May 29, 2024 16:57
@kpitzen kpitzen force-pushed the KP/RayServiceAutoscalingNoReplacement branch from 1918c4e to c992bd8 Compare May 29, 2024 16:58
@kevin85421 kevin85421 self-assigned this May 29, 2024
@kevin85421 kevin85421 self-requested a review May 29, 2024 18:06
@kevin85421 kevin85421 merged commit aeb8b03 into ray-project:master May 29, 2024
24 checks passed
@kpitzen kpitzen deleted the KP/RayServiceAutoscalingNoReplacement branch May 30, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants