Actions
Bug #46456
closedOLH entries pending removal get mistakenly resharded to shard 0
% Done:
0%
Source:
Tags:
reshard olh
Backport:
nautilus octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
When rgw_bucket_unlink_instance removes the last instance of a name, it also clears the value of rgw_bucket_olh_entry.key. However, bucket index resharding uses this key when choosing its shard placement, so an empty key causes all of these olh entries to be misplaced in shard 0. After reshard, all of the olh recovery/cleanup logic would be sent to the correct shard, and these misplaced olh entries would never be cleaned up.
Updated by Casey Bodley almost 4 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 36015
Updated by J. Eric Ivancich over 3 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46949: octopus: OLH entries pending removal get mistakenly resharded to shard 0 added
Updated by Nathan Cutler over 3 years ago
- Copied to Backport #46950: nautilus: OLH entries pending removal get mistakenly resharded to shard 0 added
Updated by Nathan Cutler over 3 years ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions