Bug with mismatched expiring_objects_container_divisor settings
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Object Storage (swift) |
Fix Released
|
Undecided
|
gholt |
Bug Description
There's an annoying bug with the object expiration feature where if you have mismatched expiring_
Not good as the info ends up in an essentially orphaned container, though the info should eventually get back to the right place with replication, I haven't confirmed that yet. And I'm pretty sure any orphaned containers would remain orphaned forever. I'll submit a tool for finding and cleaning up such orphans later.
The fix will be to pass the proxy chosen container name down to the object server along with the other information.
Note that this isn't a problem if you've always used the same expiring_
Changed in swift: | |
assignee: | nobody → gholt (gholt) |
status: | New → In Progress |
Changed in swift: | |
milestone: | none → 1.9.0 |
Changed in swift: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/31584
Review: https:/