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

Cherry-pick Serve lightweight config update telemetry #34070

Merged
merged 1 commit into from
Apr 5, 2023

Conversation

zcin
Copy link
Contributor

@zcin zcin commented Apr 4, 2023

Why are these changes needed?

Cherry pick #34039

Related issue number

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 :(

@zcin zcin marked this pull request as ready for review April 5, 2023 04:32
Copy link
Collaborator

@zhe-thoughts zhe-thoughts left a comment

Choose a reason for hiding this comment

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

Approved. cc @clarng

@clarng clarng added release-blocker P0 Issue that blocks the release v2.4.0-pick labels Apr 5, 2023
@clarng
Copy link
Contributor

clarng commented Apr 5, 2023

This change adds new telemetry to get more insight into if and how users are using the lightweight config updates feature of Serve. It adds the telemetry tags:
- `SERVE_NUM_REPLICAS_UPDATED`: whether `num_replicas` was updated (without any heavyweight option updated)
- `SERVE_USER_CONFIG_UPDATED`: whether `user_config` was updated (without any heavyweight option updated)
- `SERVE_AUTOSCALING_CONFIG_UPDATED`: whether `autoscaling_config` was updated (without any heavyweight option updated)

These values are set to True as long as the user uses the feature at least once for any deployment in any application on the cluster.

Signed-off-by: Cindy Zhang <[email protected]>
@zcin
Copy link
Contributor Author

zcin commented Apr 5, 2023

@zcin can you fix DCO?

Fixed!

Also are these failures related: https://buildkite.com/ray-project/oss-ci-build-pr/builds/17450#01874e1c-060b-42f0-b3e6-e4419a2ffc18

No, these failures are unrelated to this PR and also failing on master. I have a fix for the gradio docs tests but it's only a docs examples fix and doesn't affect Ray, so shouldn't need to cherry pick it in unless we want to get rid of the red tests on the release branch.

@clarng clarng merged commit 44d4e58 into ray-project:releases/2.4.0 Apr 5, 2023
@zcin zcin deleted the cp-b4938 branch September 8, 2023 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker P0 Issue that blocks the release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants