Project

General

Profile

Actions

Bug #40903

closed

rgw: gc remove tag issue

Added by Tianshan Qu almost 5 years ago. Updated about 3 years ago.

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

0%

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

Description

Alternate Text

Currently a gc tag is removed once the first shadow object is removed. That is problematic since if there is a failure in removing the rest of the shadow objects, there's no record to do so.

Instead we should only remove the gc tag once all the shadow objects are successfully removed.

Original Text

now gc add tag to remove queue just after first shadow io finish,
so if following shadows have any delete failure, there will be no chance to retry, since gc tag entry have been removed.


Related issues 3 (0 open3 closed)

Copied to rgw - Backport #41636: nautilus: rgw: gc remove tag issueResolvedNathan CutlerActions
Copied to rgw - Backport #41637: luminous: rgw: gc remove tag issueRejectedActions
Copied to rgw - Backport #41638: mimic: rgw: gc remove tag issueResolvedNathan CutlerActions
Actions #2

Updated by Casey Bodley over 4 years ago

  • Status changed from New to Fix Under Review
Actions #3

Updated by J. Eric Ivancich over 4 years ago

  • Description updated (diff)
  • Status changed from Fix Under Review to 17
  • Target version set to v15.0.0
  • Backport set to nautilus,mimic,luminous
  • Pull request ID set to 29199
Actions #4

Updated by J. Eric Ivancich over 4 years ago

  • Assignee set to Tianshan Qu
Actions #5

Updated by Casey Bodley over 4 years ago

  • Status changed from 17 to 7
Actions #6

Updated by Casey Bodley over 4 years ago

  • Status changed from 7 to Pending Backport
Actions #7

Updated by Nathan Cutler over 4 years ago

Actions #8

Updated by Nathan Cutler over 4 years ago

Actions #9

Updated by Nathan Cutler over 4 years ago

Actions #10

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".

Actions

Also available in: Atom PDF