Project

General

Profile

Bug #39487

rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them

Added by Casey Bodley about 2 years ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
-
% Done:

0%

Source:
Tags:
multisite trim
Backport:
luminous mimic nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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

Related to rgw - Bug #39283: rgw multisite: bucket index logs do not get trimmed unless zones 'sync_from_all' Resolved
Copied to rgw - Backport #40629: mimic: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them Resolved
Copied to rgw - Backport #40630: nautilus: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them Resolved
Copied to rgw - Backport #40631: luminous: rgw multisite: datalogs/bilogs are not trimmed if no peer zones are processing them Rejected

History

#1 Updated by Casey Bodley about 2 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 about 2 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 27794

#3 Updated by Casey Bodley almost 2 years ago

  • Status changed from Fix Under Review to Pending Backport

#4 Updated by Nathan Cutler almost 2 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 almost 2 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 almost 2 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 3 months 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".

Also available in: Atom PDF