-
Notifications
You must be signed in to change notification settings - Fork 246
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
[request]: S3 DNS re-lookup on retry #160
Comments
Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one. |
Bad bot. |
That the SDK doesn't do DNS lookup on retry is actually a bug, so I'm correcting the label on this. |
Issue in hyper that tracks making this possible: hyperium/hyper#2605 |
|
Community Note
Tell us about your request
I would like the ability to tell the S3 client to force a DNS lookup when retrying a request. This is a recommendation from S3 to improve latency.
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
This is one of the latency improvements suggested by S3:
https://docs.aws.amazon.com/AmazonS3/latest/userguide/optimizing-performance-design-patterns.html
Are you currently working around this issue?
We're not, but we looked into it. We're currently using Rusoto, which would require us to create a custom HttpConnector and create our own DNS retry logic inside of it. It's possible, but would be a pain and require several modifications.
The text was updated successfully, but these errors were encountered: