Set time-to-live on replication backups
Bug #1444558 reported by
Morgan Jones
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack DBaaS (Trove) |
Confirmed
|
Undecided
|
Morgan Jones | ||
Bug Description
When creating slaves, the replication feature creates a backup and stores it in swift. The backup is removed after the slave is created, but should the process fail the backup would be orphaned. We should use the X-Deleted-After header to set a time-to-live on the backup so that it would be eventually be cleaned up.
Suggest a time-to-live of 30 days; longer than necessary, but extremely unlikely to cause an issue with the replication process.
| Changed in trove: | |
| assignee: | nobody → Morgan Jones (6-morgan) |
| Changed in trove: | |
| status: | New → Confirmed |
Revision history for this message
| Amrith Kumar (amrith) wrote | #1 |
To post a comment you must log in.
morgan, any updates on this?