db replicator race leaves temporary database in tmp dir
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
There's probably more than one reason a remote container-
But one common way seems to be a race when two (or more) remote container-
If the database is large and the network busy - it's not uncommon to hit such a wide race.
When it does then the loser will miss some cleanup code:
While it's probably reasonable to avoid some sort of sync/merge and return the 404 error - before doing so the local container server should cleanup the temporary db which the remote is trying to tell us about.
Otherwise it *will* get reaped if it's older than a reclaim age (lp bug #1691565)
description: | updated |
Changed in swift: | |
importance: | Undecided → Medium |
status: | New → Confirmed |