Bug #1567
closedrgw [list|delete]_bucket should clean up
0%
Description
We've discussed how to clean up properly if the bucket index has unfinished ops, and it needs to be implemented:
During listing, if the reader discovers objects with uncommitted operations, it looks at the actual state of the object and reports those results. It then trims any sufficiently old (24 hours?) tag operations out of the index. If there are no remaining tags, it then updates the index to include the actual state of the object. For this purpose, the delete flag is considered an uncommitted operation -- if it is set, the reader must check the state of the object, and remove it from the index if the object no longer exists and there are no in-date tags. (If the object does exist and there are no in-date tags, it must remove the flag.)
Updated by Sage Weil over 12 years ago
- Target version changed from v0.37 to v0.38
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position set to 67
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position deleted (
67) - Translation missing: en.field_position set to 65
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_story_points set to 5
- Translation missing: en.field_position deleted (
73) - Translation missing: en.field_position set to 72
Updated by Greg Farnum over 12 years ago
- Status changed from New to Resolved
Merged into master in commit:40b7b57239515bd0794ef5da2477a2c5eb7a85e4.
Passed s3tests with a greatly-reduced timeout (20 seconds) and disablement of the directory cleanup.
Updated by John Spray over 6 years ago
- Project changed from Ceph to rgw
- Category deleted (
22) - Target version deleted (
v0.38)
Bulk reassign of radosgw category to RGW project.