Bug 1211431
| Summary: | rgw deleting S3 objects leaves __shadow_ objects behind | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Andrew Hatfield <ahatfiel> | ||||
| Component: | RGW | Assignee: | Yehuda Sadeh <yehuda> | ||||
| Status: | CLOSED ERRATA | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 1.3.0 | CC: | cbodley, ceph-eng-bugs, ceph-qe-bugs, dblack, flucifre, icolle, kbader, kdreyer, mbenjamin, owasserm, sweil, tganguly, tmuthami, yehuda | ||||
| Target Milestone: | rc | ||||||
| Target Release: | 1.3.1 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-07-16 22:20:06 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: | |||||||
| Attachments: |
|
||||||
|
Description
Andrew Hatfield
2015-04-14 01:40:00 UTC
Added to errata priority backlog, https://trello.com/c/Oe0e5vVk/11-1-3-0-async-rhel-rgw-civet-garbage-collection Does not fix previously leaked objects. For previously leaked objects there's a need for a separate tool that I worked a while back, but it's not done yet. missing qa_ack I am able to reproduce the same issue with the latest Async release. Even after deleting all the Objects i can see the shadow copies are not getting deleted.
[root@Cluster1 ~]# rpm -qa |grep ceph
ceph-osd-0.94.1-15.el7cp.x86_64
ceph-common-0.94.1-15.el7cp.x86_64
ceph-0.94.1-15.el7cp.x86_64
ceph-mon-0.94.1-15.el7cp.x86_64
ceph-deploy-1.5.25-1.el7cp.noarch
[root@RGW ~]# rpm -qa |grep ceph
ceph-radosgw-0.94.1-15.el7cp.x86_64
ceph-common-0.94.1-15.el7cp.x86_64
Please find the attached script for the operations which i performed.
I can still see lots the
"default.4194.22__shadow_.Zba-hrAA_StUHa3y4SFkURAlxjmXAs9_3"
being present after i delete all the objects created.
Even the
root@Cluster1 ~]# ceph df
GLOBAL:
SIZE AVAIL RAW USED %RAW USED
3460G 3457G 2455M 0.07
AND
[root@Cluster1 ~]# rados df
pool name KB objects clones degraded unfound rd rd KB wr wr KB
.rgw 1 2 0 0 0 278 210 133 28
.rgw.buckets 972800 300 0 0 0 3312 609 28321 11264003
.rgw.buckets.index 0 3 0 0 0 4543 4598 3283 0
.rgw.control 0 8 0 0 0 0 0 0 0
.rgw.gc 0 32 0 0 0 2909 4383 2334 0
.rgw.root 1 3 0 0 0 45 30 3 3
.users 1 2 0 0 0 2 1 2 2
.users.swift 1 1 0 0 0 2 1 1 1
.users.uid 1 2 0 0 0 135 131 75 3
rbd 0 0 0 0 0 0 0 0 0
total used 2514728 353
total avail 3625606264
total space 3628120992
I used the puddle to upgrade my Cluster from 1.3.0 to 1.3.0_Async Release.
baseurl = http://puddle.ceph.redhat.com/puddles/RHCeph/1.3-RHEL-7/2015-07-06.2/Server-RH7-CEPH-TOOLS-1.3/x86_64/os
Created attachment 1050680 [details]
Test Script
Not sure I understand how the test script relates to this bug. So you create a few objects, sleep 1200 seconds (20 minutes), then delete them? The idea is to create the objects, delete them, then wait past the garbage collector's period (minimum of 2 hours, should wait more). Thanks Yehuda, I got it...To clean up the shadows copies it takes time i didn't know. (GC to take 2 hours or more) Just checked again in my Cluster and saw all the shadow copies are deleted. Hence its working fine as per the Bug, marking it as verified. PS: The sleep was just like that ( I wanted to check my Cluster state and object copies ) [root@RGW ~]# rpm -qa |grep ceph ceph-radosgw-0.94.1-15.el7cp.x86_64 ceph-common-0.94.1-15.el7cp.x86_64 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-2015:1240 |