Actions
Bug #40187
closedmultisite: 'radosgw-admin bilog trim' stops after 1000 entries
% Done:
0%
Source:
Tags:
multisite trim
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
The CLSRGWIssueBILogTrim class is intended to keep submitting cls_log_trim operations on each bucket index shard until they return -ENODATA to signal there's no more to trim.
However, if the while loop in CLSRGWConcurrentIO::operator() gets to the end of the shard list and collects all of its completions, wait_for_completions() will return false and exit the loop. This is always the case when num_shards = 1.
$ radosgw-admin bilog list --bucket testbucket --max-entries 99999 | jq length 5328 $ radosgw-admin bilog trim --bucket testbucket --end-marker 9 $ radosgw-admin bilog list --bucket testbucket --max-entries 99999 | jq length 4328
Updated by Casey Bodley almost 5 years ago
- Status changed from New to Fix Under Review
- Assignee set to Casey Bodley
- Pull request ID set to 28430
Updated by Casey Bodley almost 5 years ago
- Status changed from Fix Under Review to 7
Updated by Casey Bodley almost 5 years ago
- Status changed from 7 to Pending Backport
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40538: luminous: multisite: 'radosgw-admin bilog trim' stops after 1000 entries added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40539: mimic: multisite: 'radosgw-admin bilog trim' stops after 1000 entries added
Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #40540: nautilus: multisite: 'radosgw-admin bilog trim' stops after 1000 entries 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