Project

General

Profile

Actions

Bug #37339

closed

rgw: resharding leaves old bucket info objs and index shards behind

Added by J. Eric Ivancich over 5 years ago. Updated about 5 years ago.

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

0%

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

Description

The resharding process does not delete formerly used bucket info objects or index shards. Additionally, should a resharding attempt fail, an unfinished bucket info obj and associated index shards will be left behind. These two code pathways leave an accumulation of unneeded objects and omap entries, which should be removed automatically.


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #37554: mimic: rgw: resharding leaves old bucket info objs and index shards behindResolvedAbhishek LekshmananActions
Copied to rgw - Backport #37555: luminous: rgw: resharding leaves old bucket info objs and index shards behindResolvedAbhishek LekshmananActions
Actions #2

Updated by J. Eric Ivancich over 5 years ago

  • Subject changed from rgw: resharding leaves old bucket info objs and shards behind to rgw: resharding leaves old bucket info objs and index shards behind
Actions #3

Updated by J. Eric Ivancich over 5 years ago

  • Description updated (diff)
Actions #4

Updated by Casey Bodley over 5 years ago

  • Status changed from In Progress to Pending Backport
Actions #5

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #37554: mimic: rgw: resharding leaves old bucket info objs and index shards behind added
Actions #6

Updated by Nathan Cutler over 5 years ago

  • Copied to Backport #37555: luminous: rgw: resharding leaves old bucket info objs and index shards behind added
Actions #7

Updated by Nathan Cutler about 5 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF