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

[Data] Add SERVICE_UNAVAILABLE to list of retried transient errors #47673

Merged
merged 1 commit into from
Sep 16, 2024

Conversation

bveeramani
Copy link
Member

Why are these changes needed?

While reading or writing files with Ray Data, S3 might raise a transient SERVICE_UNAVAILABLE error. This PR adds the error to the list of retried transient errors.

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

Signed-off-by: Balaji Veeramani <[email protected]>
@@ -114,6 +116,7 @@
"AWS Error NETWORK_CONNECTION",
"AWS Error SLOW_DOWN",
"AWS Error UNKNOWN (HTTP status 503)",
"AWS Error SERVICE_UNAVAILABLE",
Copy link
Contributor

Choose a reason for hiding this comment

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

should we also add this to DEFAULT_RETRIED_IO_ERRORS?

Copy link
Member Author

Choose a reason for hiding this comment

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

It is in it. You might need to expand the diff
image

Copy link
Contributor

Choose a reason for hiding this comment

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

oh sorry i got confused by the top comment above DEFAULT_WRITE_FILE_RETRY_ON_ERRORS. for backwards compatibility, should we also add it in DEFAULT_WRITE_FILE_RETRY_ON_ERRORS?

Copy link
Member Author

@bveeramani bveeramani Sep 16, 2024

Choose a reason for hiding this comment

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

DEFAULT_WRITE_FILE_RETRY_ON_ERRORS isn't used anywhere right now. If you try to configure write_file_retry_on_errors, Ray Data emits a warning instructing you to configure retried_io_errors instead.

@bveeramani bveeramani enabled auto-merge (squash) September 16, 2024 17:34
@github-actions github-actions bot added the go add ONLY when ready to merge, run all tests label Sep 16, 2024
@bveeramani bveeramani merged commit 9495e72 into master Sep 16, 2024
6 checks passed
@bveeramani bveeramani deleted the retry-service-unavailable branch September 16, 2024 18:34
simonsays1980 pushed a commit to simonsays1980/ray that referenced this pull request Sep 17, 2024
…ay-project#47673)

While reading or writing files with Ray Data, S3 might raise a transient SERVICE_UNAVAILABLE error. This PR adds the error to the list of retried transient errors.

Signed-off-by: Balaji Veeramani <[email protected]>
ujjawal-khare pushed a commit to ujjawal-khare-27/ray that referenced this pull request Oct 15, 2024
…ay-project#47673)

While reading or writing files with Ray Data, S3 might raise a transient SERVICE_UNAVAILABLE error. This PR adds the error to the list of retried transient errors.

Signed-off-by: Balaji Veeramani <[email protected]>
Signed-off-by: ujjawal-khare <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants