From: Abhishek Lekshmanan Date: Thu, 2 May 2019 13:25:22 +0000 (+0200) Subject: doc: add a troubleshooting note on resharding expirer fixes X-Git-Tag: v15.1.0~2690^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=40bf082da29450ca711bffd9df56b2b14a5a71c4;p=ceph.git doc: add a troubleshooting note on resharding expirer fixes Added a note about the commands added to support stale expired object deletion Signed-off-by: Abhishek Lekshmanan --- diff --git a/doc/radosgw/dynamicresharding.rst b/doc/radosgw/dynamicresharding.rst index d802b4ee18c7..5fb5063b76a9 100644 --- a/doc/radosgw/dynamicresharding.rst +++ b/doc/radosgw/dynamicresharding.rst @@ -143,3 +143,30 @@ The command to do so is: As a convenience wrapper, if the ``--bucket`` argument is dropped then this command will try and fix lifecycle policies for all the buckets in the cluster. + +Object Expirer fixes +-------------------- + +Objects subject to Swift object expiration on older clusters may have +been dropped from the log pool and never deleted after the bucket was +resharded. This would happen if their expiration time was before the +cluster was upgraded, but if their expiration was after the upgrade +the objects would be correctly handled. To manage these expire-stale +objects, radosgw-admin provides two subcommands. + +Listing: + +:: + + # radosgw-admin objects expire-stale list --bucket {bucketname} + +Displays a list of object names and expiration times in JSON format. + +Deleting: + +:: + + # radosgw-admin objects expire-stale rm --bucket {bucketname} + + +Initiates deletion of such objects, displaying a list of object names, expiration times, and deletion status in JSON format.