-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Conversation
There was a problem hiding this 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)?
There was a problem hiding this 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)?
Yup |
There was a problem hiding this 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?
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. |
travis gave up https://travis-ci.com/github/ray-project/ray/builds/231132106#L1904 |
test failures all look like unrelated rllib tests. travis timeout also looks unrelated. merging. |
Co-authored-by: Alex <alex@anyscale.com>
This reverts commit 6aca77a.
Co-authored-by: Alex <alex@anyscale.com>
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
scripts/format.sh
to lint the changes in this PR.