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

[core][autoscaler] Fix pg id serialization with hex rather than binary for cluster state reporting #37132 #37176

Merged

Conversation

rickyyx
Copy link
Contributor

@rickyyx rickyyx commented Jul 6, 2023

Why are these changes needed?

The labels are declared as strings, and PG will generate (anti)affinity labels. The current implementation geneates PG<binary_pg_id> as the label key. However, binary chars are not encodable in string.

This PR changes the pg generated dynamic labels to PG<hex_pg_id> which is more readable as well.

Why are these changes needed?

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

…y for cluster state reporting ray-project#37132

Why are these changes needed?
The labels are declared as strings, and PG will generate (anti)affinity labels. The current implementation geneates _PG_<binary_pg_id> as the label key. However, binary chars are not encodable in string.

This PR changes the pg generated dynamic labels to _PG_<hex_pg_id> which is more readable as well.
@rickyyx
Copy link
Contributor Author

rickyyx commented Jul 6, 2023

For autoscaler v2.

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.

Change seems clean enough and is necessary for a project deadline. Let's pick

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.

4 participants