-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Retry on ResponseStreamingError
when getting s3 objects.
#4111
Comments
Hi @adriancaruana thanks for reaching out. In the issue you linked (boto/botocore#3132) it looks like this was fixed via boto/s3transfer#301 for urllib3 2+. Could you try updating your versions of Boto3/urllib3? The latest Boto3 version is 1.34.99 per the CHANGELOG. Or if you could at least try testing in 1.34.63 / urllib3 2.2.1+. |
Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one. |
@tim-finnigan looks like the fix is only for s3transfer, does that apply to get_object? My understanding is get_object is not handling ResponseStreamingError explicitly? |
Describe the feature
Include
ResponseStreamingError
in the list of "standard" errors/exceptions that are retried when getting s3 objects.Use Case
I'm getting
ResponseStreamingError
sometimes when doing.get_object
with an s3 client. Even when my client is configured with retries, the client does not retry when this exception is raised.The following code reproduces the error:
Proposed Solution
No response
Other Information
The following issue might be related: boto/botocore#3132
Acknowledgements
SDK version used
1.34.51
Environment details (OS name and version, etc.)
Ubuntu, python 3.11.8, urllib3 1.26.18
The text was updated successfully, but these errors were encountered: