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.

Sign up for GitHub

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

Jump to bottom

Light weight resource broadcasting testing #30631

Closed
fishbone opened this issue Nov 23, 2022 · 0 comments · Fixed by #30460
Closed

Light weight resource broadcasting testing #30631

fishbone opened this issue Nov 23, 2022 · 0 comments · Fixed by #30460
Assignees
@fishbone
Labels
core Issues that should be addressed in Ray Core

Comments

@fishbone
Copy link
Contributor

Right now, RPC failure is not handled well in light weight resource broadcasting which will leads to resource view stale in case of failure.

To handle the failure is not so straightforward given that there are states in each side.

We should change the resource broadcasting from unary API to streaming ones which simplify a lot of thins:

  • We don't need long polling
  • Error handling is easier
  • RPC interface is easier
  • More efficient.
@fishbone fishbone self-assigned this Nov 23, 2022
@fishbone fishbone added the core Issues that should be addressed in Ray Core label Nov 23, 2022
@fishbone fishbone linked a pull request Nov 23, 2022 that will close this issue
[core][scalability] Change ray syncer from unary call to streaming call #30460
Merged
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fishbone fishbone

Labels
core Issues that should be addressed in Ray Core
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[core][scalability] Change ray syncer from unary call to streaming call fishbone/ray
1 participant
@fishbone