Bug 1653830

Summary: rgw: resharding does not drop old bucket indexes or bucket info objects; needs CLI clean-up tool for existing clusters
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: J. Eric Ivancich <ivancich>
Component: RGWAssignee: J. Eric Ivancich <ivancich>
Status: CLOSED ERRATA QA Contact: Tejas <tchandra>
Severity: low Docs Contact:
Priority: high    
Version: 3.2CC: cbodley, ceph-eng-bugs, ceph-qe-bugs, kbader, mbenjamin, sweil, tchandra, tserlin
Target Milestone: rc   
Target Release: 3.2   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: RHEL: ceph-12.2.8-43.el7cp Ubuntu: ceph_12.2.8-38redhat1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-03 19:02:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description J. Eric Ivancich 2018-11-27 17:34:40 UTC
Resharding, whether dynamic or manual, has not previously clean up the old bucket info objects or shard objects. That has led to an accumulation of unneeded objects that likely impacts performance.

BZ#1627562 addresses one aspect of this issue, and automatically cleans up these objects after both successful and failed reshardings. But for existing clusters that have experienced this accumulation of unneeded objects, we need an administrative tool to clean these up.

See also:

    https://bugzilla.redhat.com/show_bug.cgi?id=1627562

Comment 3 J. Eric Ivancich 2018-11-27 17:38:29 UTC
Upstream this issue is tracker: http://tracker.ceph.com/issues/24082

The solution is a backport of PR https://github.com/ceph/ceph/pull/24662

Comment 10 errata-xmlrpc 2019-01-03 19:02:25 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0020