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] Retry failed redis request (#35249) #35481

Merged

Conversation

fishbone
Copy link
Contributor

@fishbone fishbone commented May 18, 2023

Why are these changes needed?

This cherry-picks #35249

After #35123 the request in ray is serialized and we should be able to retry the failed redis request in ray.

This PR refactor the RedisContext a little bit by remove the CallbackItem and introduce the RequestContext. In side the RequestContext, the failed request will be retried automatically.

If still failed in the end, it'll just crash.

Related issue number

#34014

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

## Why are these changes needed?
<!-- Please give a short summary of the change and the problem this solves. -->
After ray-project#35123 the request in ray is serialized and we should be able to retry the failed redis request in ray.

This PR refactor the RedisContext a little bit by remove the CallbackItem and introduce the RequestContext. In side the RequestContext, the failed request will be retried automatically.

If still failed in the end, it'll just crash.

## Related issue number
ray-project#34014
@fishbone fishbone requested a review from a team as a code owner May 18, 2023 00:22
Copy link
Collaborator

@zhe-thoughts zhe-thoughts left a comment

Choose a reason for hiding this comment

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

Approved for picking into 2.5.0 since this is a release blocker

@ArturNiederfahrenhorst ArturNiederfahrenhorst merged commit 64e4926 into ray-project:releases/2.5.0 May 19, 2023
architkulkarni added a commit to architkulkarni/ray that referenced this pull request May 19, 2023
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.

4 participants