-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
[Client] Disconnect on dataclient error #16588
[Client] Disconnect on dataclient error #16588
Conversation
3f57979
to
502d0ac
Compare
8817342
to
6f56625
Compare
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!
@DmitriGekhtman , if this is not too much work, it would be nice to include this PR as well in 1.4.1 |
b3bbec6
to
c26ab22
Compare
Rebased with master to fix failing java test, reviewers can merge at their discretion once everything is passing. |
sure, np -- any additional release testing required? |
No. Thanks! |
test_array, test_async are both known flakey on windows -- travis build failure is widespread |
* disconnect when main thread finds dataclient shut down, update error messages * Add test_dataclient_disconnect to small tests * drop unused var * add __main__ section to test * avoid direct ray import * rerun
Why are these changes needed?
When the data client's grpc channel disconnects (either for connection issues, or for a bad request) client is left in a state where it can't perform any remote functionality, but is still technically connected (client_ray.is_connected() is True).Since is_connected() still returns True, this causes errors if the user tries to start a new connection. This PR disconnects the client when the data client is found to be shut down by the main thread so that the user can cleanly try to reconnect.
Related issue number
Checks
scripts/format.sh
to lint the changes in this PR.