Opened at 2013-08-29T13:20:57Z
Closed at 2020-10-30T12:35:44Z
#2068 closed defect (wontfix)
cloud.s3 backend: investigate DNS failures; possibly fall back to bucket-in-path for retries if bucket-in-host fails
| 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.)
Change History (7)
comment:1 Changed at 2013-08-29T13:21:40Z by daira
- Description modified (diff)
comment:2 Changed at 2015-01-29T19:53:36Z by daira
- Milestone changed from undecided to 1.11.0
comment:3 Changed at 2015-02-08T23:52:56Z by daira
- Milestone changed from 1.11.0 to 1.12.0
comment:4 Changed at 2016-03-22T05:02:25Z by warner
- Milestone changed from 1.12.0 to 1.13.0
comment:5 Changed at 2016-06-28T18:17:14Z by warner
- Milestone changed from 1.13.0 to 1.14.0
renaming milestone
comment:6 Changed at 2020-06-30T14:45:13Z by exarkun
- Milestone changed from 1.14.0 to 1.15.0
Moving open issues out of closed milestones.
comment:7 Changed at 2020-10-30T12:35:44Z by exarkun
- Resolution set to wontfix
- Status changed from new to closed
The established line of development on the "cloud backend" branch has been abandoned. This ticket is being closed as part of a batch-ticket cleanup for "cloud backend"-related tickets.
If this is a bug, it is probably genuinely no longer relevant. The "cloud backend" branch is too large and unwieldy to ever be merged into the main line of development (particularly now that the Python 3 porting effort is significantly underway).
If this is a feature, it may be relevant to some future efforts - if they are sufficiently similar to the "cloud backend" effort - but I am still closing it because there are no immediate plans for a new development effort in such a direction.
Tickets related to the "leasedb" are included in this set because the "leasedb" code is in the "cloud backend" branch and fairly well intertwined with the "cloud backend". If there is interest in lease implementation change at some future time then that effort will essentially have to be restarted as well.
Milestone renamed