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

[Autoscaler] make --redis-address not required #22083

Merged
merged 3 commits into from
Feb 10, 2022

Conversation

mwtian
Copy link
Member

@mwtian mwtian commented Feb 3, 2022

Why are these changes needed?

--redis-address should not be required, since starting autoscaler with --gcs-address is supported too.

Related issue number

Checks

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

Copy link
Contributor

@DmitriGekhtman DmitriGekhtman left a comment

Choose a reason for hiding this comment

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

This LGTM.
Can we also modify the "ray start" sequence to not pass a Redis address if bootstrapping with gcs, rather than passing "None"

@DmitriGekhtman
Copy link
Contributor

(I mean modify to not pass "redis-address" to the monitor entry-point)

@mwtian mwtian added the tests-ok The tagger certifies test failures are unrelated and assumes personal liability. label Feb 10, 2022
@mwtian
Copy link
Member Author

mwtian commented Feb 10, 2022

The test_dataset failure looks unrelated.

@fishbone fishbone merged commit 9bc6f13 into ray-project:master Feb 10, 2022
simonsays1980 pushed a commit to simonsays1980/ray that referenced this pull request Feb 27, 2022
`--redis-address` should not be required, since starting autoscaler with `--gcs-address` is supported too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tests-ok The tagger certifies test failures are unrelated and assumes personal liability.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants