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

Same worker id in python and c++ (try #2) #16712

Merged
merged 1 commit into from
Jun 28, 2021

Conversation

wuisawesome
Copy link
Contributor

@wuisawesome wuisawesome commented Jun 28, 2021

Why are these changes needed?

This PR makes the log files for the C++ core worker, and corresponding python worker consistent. It makes the c++ worker the only place that generates worker ids.

Related issue number

Closes #16127

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

@wuisawesome
Copy link
Contributor Author

cc @kfstorm @rkooo567

Copy link
Contributor

@ijrsvt ijrsvt left a comment

Choose a reason for hiding this comment

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

@wuisawesome
The main difference between this PR and #16568 is that this PR makes C++ the source of truth (whereas the previous attempt used Python)?

Copy link
Contributor

@ijrsvt ijrsvt left a comment

Choose a reason for hiding this comment

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

@wuisawesome
The main difference between this PR and #16568 is that this PR makes C++ the source of truth (whereas the previous attempt used Python)?

@wuisawesome
Copy link
Contributor Author

Yup

Copy link
Contributor

@ijrsvt ijrsvt left a comment

Choose a reason for hiding this comment

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

LGTM! Should we also do this for Java?

@wuisawesome
Copy link
Contributor Author

From @kfstorm's comment here, I think Java already let the core worker generate the ID's, so this is really just python catching up.

#16600 (comment)

@DmitriGekhtman
Copy link
Contributor

travis gave up https://travis-ci.com/github/ray-project/ray/builds/231132106#L1904
Try rerunning?

@wuisawesome
Copy link
Contributor Author

test failures all look like unrelated rllib tests. travis timeout also looks unrelated. merging.

@wuisawesome wuisawesome merged commit 0811ae4 into ray-project:master Jun 28, 2021
DmitriGekhtman pushed a commit that referenced this pull request Jun 28, 2021
Co-authored-by: Alex <alex@anyscale.com>
DmitriGekhtman added a commit that referenced this pull request Jun 29, 2021
DmitriGekhtman pushed a commit that referenced this pull request Jun 29, 2021
Co-authored-by: Alex <alex@anyscale.com>
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.

Feature Request: Unify CPP and Python worker IDs
3 participants