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

[cherry-pick][core] Sending ReportWorkerFailure after the process died. (#35320) #35420

Closed

Conversation

fishbone
Copy link
Contributor

Why are these changes needed?

This fix is not fixing from the root #35247

And in many_nodes_actor_tests_v2, the file descriptor error still shows.

This fix tries to monitor the process's liveness in some way. It also introduce a new util function which will retry the failed function until certain number.

Some tests are disabled due to the race condition in detecting node failures which will be fixed later.

Why are these changes needed?

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 :(

…ct#35320)

## Why are these changes needed?
This fix is not fixing from the root ray-project#35247

And in many_nodes_actor_tests_v2, the file descriptor error still shows. 

This fix tries to monitor the process's liveness in some way.  It also introduce a new util function which will retry the failed function until certain number.

Some tests are disabled due to the race condition in detecting node failures which will be fixed later.
@fishbone fishbone added the release-blocker P0 Issue that blocks the release label May 17, 2023
@zhe-thoughts
Copy link
Collaborator

@iycheng After this PR lands in master, please create a cherry pick PR and add me as an assignee. Thanks! cc @ArturNiederfahrenhorst

@zhe-thoughts
Copy link
Collaborator

@iycheng actually is this PR already a cherry pick PR for t #35247? Thanks

@fishbone
Copy link
Contributor Author

@zhe-thoughts yes, this is a cherry-pick PR.

@fishbone fishbone changed the title [core] Sending ReportWorkerFailure after the process died. (#35320) [cherry-pick][core] Sending ReportWorkerFailure after the process died. (#35320) May 17, 2023
@fishbone
Copy link
Contributor Author

The master one got reverted :( I'll close this first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker P0 Issue that blocks the release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants