Skip to content

add ray io docs for app level autoscaling#57756

Merged
abrarsheikh merged 27 commits intomasterfrom
SERVE-1235-abrar-doc2
Oct 16, 2025
Merged

add ray io docs for app level autoscaling#57756
abrarsheikh merged 27 commits intomasterfrom
SERVE-1235-abrar-doc2

Conversation

@abrarsheikh
Copy link
Copy Markdown
Contributor

@abrarsheikh abrarsheikh commented Oct 15, 2025

…tate

Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
Signed-off-by: abrar <abrar@anyscale.com>
:::

:::{note}
When you specify both a deployment-level policy and an application-level policy, the application-level policy takes precedence. Ray Serve logs a warning if you configure both.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

shouldn't this be the other way around?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

We chose to have the application-level policy take precedence over deployment-level policies to ensure clarity and consistency in configuration. Maintaining an app-level policy that applies to only a subset of deployments introduces ambiguity and complexity. By enforcing app-level precedence, users have a single, authoritative source of truth for policy behavior.

Additionally, each deployment has a default policy value that cannot be easily removed, which can lead to confusion if both app-level and deployment-level policies coexist. To help users detect potential misconfigurations, Ray Serve emits a warning when both are specified.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Base automatically changed from SERVE-1227-abrar-app_auto to master October 16, 2025 03:33
Signed-off-by: abrar <abrar@anyscale.com>
@abrarsheikh abrarsheikh marked this pull request as ready for review October 16, 2025 03:43
@abrarsheikh abrarsheikh requested review from a team as code owners October 16, 2025 03:43
@abrarsheikh abrarsheikh added the go add ONLY when ready to merge, run all tests label Oct 16, 2025
Signed-off-by: abrar <abrar@anyscale.com>
cursor[bot]

This comment was marked as outdated.

@ray-gardener ray-gardener bot added serve Ray Serve Related Issue docs An issue or change related to documentation labels Oct 16, 2025
@abrarsheikh abrarsheikh merged commit 10bc0bf into master Oct 16, 2025
6 checks passed
@abrarsheikh abrarsheikh deleted the SERVE-1235-abrar-doc2 branch October 16, 2025 18:53
xinyuangui2 pushed a commit to xinyuangui2/ray that referenced this pull request Oct 22, 2025
elliot-barn pushed a commit that referenced this pull request Oct 23, 2025
Aydin-ab pushed a commit to Aydin-ab/ray-aydin that referenced this pull request Nov 19, 2025
Future-Outlier pushed a commit to Future-Outlier/ray that referenced this pull request Dec 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs An issue or change related to documentation go add ONLY when ready to merge, run all tests serve Ray Serve Related Issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants