aws-sdk-rust icon indicating copy to clipboard operation
aws-sdk-rust copied to clipboard

Published 20 hours ago • verified publisher icon awslabs

[request]: S3 DNS re-lookup on retry

Open keetonian opened this issue 4 years ago • 4 comments
trafficstars

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue, please leave a comment

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:

For latency-sensitive applications, Amazon S3 advises tracking and aggressively retrying slower operations. When you retry a request, we recommend using a new connection to Amazon S3 and performing a fresh DNS lookup.

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.

keetonian avatar Jul 20 '21 18:07 keetonian

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.

github-actions[bot] avatar Jul 21 '22 16:07 github-actions[bot]

Bad bot.

jdisanti avatar Jul 21 '22 16:07 jdisanti

That the SDK doesn't do DNS lookup on retry is actually a bug, so I'm correcting the label on this.

jdisanti avatar Jul 21 '22 16:07 jdisanti

Issue in hyper that tracks making this possible: https://github.com/hyperium/hyper/issues/2605

jdisanti avatar Sep 01 '22 18:09 jdisanti

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

github-actions[bot] avatar Mar 31 '23 01:03 github-actions[bot]