Bug 1703557 - rgw: object expirer: handle resharded buckets
Summary: rgw: object expirer: handle resharded buckets
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: RGW
Version: 3.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: 3.3
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
Aron Gunn
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
Reported: 2019-04-26 17:06 UTC by Matt Benjamin (redhat)
Modified: 2019-08-21 15:11 UTC (History)
10 users (show)

Fixed In Version: RHEL: ceph-12.2.12-34.el7cp Ubuntu: ceph_12.2.12-31redhat1
Doc Type: Bug Fix
Doc Text:
.Swift object expiration is no longer effected by resharding The Swift object expiration code was not compatible with bucket index resharding. This behavior could stall object expiration for the buckets. The Swift object expiration code has been updated to identify buckets using a tenant and bucket name. This update allows the removal of expired objects from an already resharded and stalled bucket. As a result, the object expiration is no longer effected by bucket index resharding.
Clone Of:
Last Closed: 2019-08-21 15:10:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 39495 0 None None None 2019-04-26 17:08:11 UTC
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:11:02 UTC

Description Matt Benjamin (redhat) 2019-04-26 17:06:58 UTC
From upstream tracker:

A bucket reshard causes swift object expiry to fail. While further swift client requests will still return a 404 as we check for obj expiry times in GET requests, the object is never deleted on disk, and the delete hint is already trimmed as we assume a non-findeable bucket means the bucket was deleted

$ swift upload foobar foo -H "X-Delete-After: 100" 
$ radosgw-admin bucket reshard foobar --num-shards 4 
$ sleep 100 && radosgw-admin objects expire --debug-rgw=20
$ radosgw-admin object stat --bucket foobar --object foo # returns 


Comment 7 errata-xmlrpc 2019-08-21 15:10:51 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.


Note You need to log in before you can comment on or make changes to this bug.