Bug #39487
rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them
% Done:
0%
Source:
Tags:
multisite trim
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
When no peer zones are configured to sync from a source zone, the minimum markers are empty and no entries are trimmed. The entire log should be trimmed in this case.
Related issues
History
#1 Updated by Casey Bodley almost 5 years ago
- Related to Bug #39283: rgw multisite: bucket index logs do not get trimmed unless zones 'sync_from_all' added
#2 Updated by Casey Bodley almost 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 27794
#3 Updated by Casey Bodley over 4 years ago
- Status changed from Fix Under Review to Pending Backport
#4 Updated by Nathan Cutler over 4 years ago
- Copied to Backport #40629: mimic: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them added
#5 Updated by Nathan Cutler over 4 years ago
- Copied to Backport #40630: nautilus: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them added
#6 Updated by Nathan Cutler over 4 years ago
- Copied to Backport #40631: luminous: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them added
#7 Updated by Nathan Cutler about 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".