I'm in the process of cleaning up a test that an internal customer did on our production cluster that produced over a billion objects spread across 6000 buckets. So far I've been removing the buckets like this:
printf %s\\n bucket{1..6000} | xargs -I{} -n 1 -P 32 radosgw-admin bucket rm --bucket={} --purge-objects
However, the disk usage doesn't seem to be getting reduced at the same rate the objects are being removed. From what I can tell a large number of the objects are waiting for garbage collection.
When I first read the docs it sounded like the garbage collector would only remove 32 objects every hour, but after looking through the logs I'm seeing about 55,000 objects removed every hour. That's about 1.3 million a day, so at this rate it'll take a couple years to clean up the rest! For comparison, the purge-objects command above is removing (but not GC'ing) about 30 million objects a day, so a much more manageable 33 days to finish.
I've done some digging and it appears like I should be changing these configuration options:
rgw gc max objs (default: 32)
rgw gc obj min wait (default: 7200)
rgw gc processor max time (default: 3600)
rgw gc processor period (default: 3600)
A few questions I have though are:
Should 'rgw gc processor max time' and 'rgw gc processor period' always be set to the same value?
Which would be better, increasing 'rgw gc max objs' to something like 1024, or reducing the 'rgw gc processor' times to something like 60 seconds?
Any other guidance on the best way to adjust these values?
Thanks,
Bryan
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
