Opened at 2013-08-29T13:20:57Z
Last modified at 2020-10-30T12:35:44Z
#2068 closed defect
cloud.s3 backend: investigate DNS failures; possibly fall back to bucket-in-path for retries if bucket-in-host fails — at Version 1
| Reported by: | daira | Owned by: | daira |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.15.0 |
| Component: | code-storage | Version: | cloud-branch |
| Keywords: | s3-backend ec2 dns LeastAuthority.com error txaws reliability | Cc: | |
| Launchpad Bug: |
Description (last modified by daira)
LeastAuthority.com's monitoring sees occasional DNS errors https://github.com/LeastAuthority/leastauthority.com/issues/30 when trying to resolve $BUCKETNAME.s3.amazonaws.com from an EC2 instance. It could fall back to a bucket-in-path URL for retries in this case. Alternatively, it may be that the existing retry is sufficient to mask these failures, but we need to know whether that is the case. (The monitoring code does not retry.)
(We originally switched to bucket-in-host URLs because bucket-in-path requests were sometimes failing, claiming that we were using the wrong endpoint. If that happens in the same situation as the DNS failures, then we might not be able to improve reliability by falling back to bucket-in-path.)
