Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Use GCSClient instead of PythonGCSClient #211
Use GCSClient instead of PythonGCSClient #211
Changes from 17 commits
2bfafa3
f342fa0
5e4812c
feeec48
dbc760f
7ec1c81
daf3da2
6ad9dc0
6b98717
46e1d64
b92b437
0726fef
b63369f
2cf2529
9c1edd6
123a7dc
9e15271
dff8b4f
9862a20
c49e9e3
a35ccc0
cc8f43a
49de1b5
7f6d315
0a8046b
492845b
9bb6921
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The issue here is that the
Connect
call returnsStatus::OK
irrespective of whether the GCS Server exists.It first reports after 5 seconds that it can't connect, then after a minute kills the session with an
EXIT_FAILURE
.Again these are set by
RayConfig
params.If the client does not exist then then the thread executing the server (I think) throws the error which only gets reported but not caught in the Julia REPL
https://github.com/ray-project/ray/blob/cde6e887cbb21a9cae2632e3e4b883d913d38a05/src/ray/rpc/gcs_server/gcs_rpc_client.h#L212-L216
Unfortunately the
gcs_is_down_
field is private, however there is a way to check if the server is alive that uses a callbackHowever, I don't think it's worth directly implementing this. The timeout should take care of things it's just that the error won't be nicely caught/reported in Julia but we can add that as a follow up.
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.
MWE
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.
The scenario in which this would occur is if you run
Ray.init()
without a local raylet present? If so, I'm fine with making this into an issue to tackle later.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.
yeah and even then it should error earlier if it tried to get the GCS address during
Ray.init