Actions
Bug #40818
closedmultisite: versioned bucket deletion sometimes fails with BucketNotEmpty
% Done:
0%
Source:
Tags:
multisite
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
On the master zone A, after deleting the contents of a bucket that contains delete markers, a bucket deletion request may fail with BucketNotEmpty if the removal of the delete markers races with a full sync from the secondary zone B. If full sync gets a bucket listing from the zone B that includes a delete marker, zone A will recreate that delete marker. That delete marker will be deleted again when it gets to incremental sync, but an attempt to delete the bucket before that will fail with BucketNotEmpty.
Updated by Casey Bodley almost 5 years ago
- Status changed from New to In Progress
- Assignee set to Casey Bodley
Updated by Casey Bodley almost 5 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 29235
Updated by Casey Bodley over 4 years ago
- Status changed from Fix Under Review to 4
Updated by Casey Bodley over 4 years ago
- Status changed from 4 to Won't Fix
this is just a consequence of eventually-consistent async replication
Actions