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

[core] Fix a corner case where QueryAllWorkerStates never return #37496

Merged
merged 2 commits into from
Jul 19, 2023

Conversation

fishbone
Copy link
Contributor

Why are these changes needed?

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • 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 added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • 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 :(

@@ -922,6 +925,9 @@ void NodeManager::QueryAllWorkerStates(
}
});
}
if(all_dead) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
if(all_dead) {
if (all_dead) {

@rkooo567
Copy link
Contributor

Wonder if we can also add timeout?

@fishbone
Copy link
Contributor Author

Wonder if we can also add timeout?

maybe it's ok. if the worker died, it'll return failure. otherwise, it'll just retry I think?

@rkooo567
Copy link
Contributor

I think we don't have retry there. One potential problem is the worker being overloaded and never reply, which hangs the reply of the RPC. I don't think we need to handle this in this PR

@fishbone fishbone merged commit 45655b7 into ray-project:master Jul 19, 2023
113 of 116 checks passed
Bhav00 pushed a commit to Bhav00/ray that referenced this pull request Jul 24, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.
NripeshN pushed a commit to NripeshN/ray that referenced this pull request Aug 15, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.

Signed-off-by: NripeshN <[email protected]>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.

Signed-off-by: harborn <[email protected]>
harborn pushed a commit to harborn/ray that referenced this pull request Aug 17, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.
arvind-chandra pushed a commit to lmco/ray that referenced this pull request Aug 31, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.

Signed-off-by: e428265 <[email protected]>
vymao pushed a commit to vymao/ray that referenced this pull request Oct 11, 2023
…-project#37496)

In some extreme cases, when the worker becomes dead after getting the workers, the RPC request might never return.

This PR fixed this issue.

Signed-off-by: Victor <[email protected]>
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.

None yet

2 participants