Re: rgw index auto resharding not acting
I looks like "limit check" counts _all_ objects, but the resharder only uses stats from rgw.main. Is that correct?
If so, why? Shouldn't the auto-resharding act on the total number of objects in the bucket?
I have around 5 million objects in rgw.none and 3 mil in rgw.main... limit check reports 8-9 million objects.
In the older days, ceph sometimes got confused an thought there were 18 billion million objects belonging to the category rgw.none, and based its reshard decisions on that, which also wasn't so good. -- May the most significant bit of your life be positive.
In the older days, ceph sometimes got confused an thought there were 18 billion million objects belonging to the category rgw.none, and based its reshard decisions on that, which also wasn't so good.
-- May the most significant bit of your life be positive.
I figured that my rgw.none objects stem from bucket versioning being "suspended". This creates a bunch of delete markers with versionId=null. I wish there was a tool to prune those objects, in the case that I never want object versioning again. Rather than creating a new bucket and copying all content.
participants (2)
-
Janne Johansson
-
Johan Thomsen