Hi Cephers, we are running Ceph RGW with bucket versioning enabled (currently on Reef, but we have also observed the same behavior on other releases). We are seeing an operational issue where a single object key can accumulate extremely large numbers of versions (hundreds of thousands up to millions). Because all versions of the same key are stored on the same bucket index shard, this results in very large bucket-index entries / omap growth and shard hotspots. In our case, one object with millions of versions caused significant bucket index pressure and related performance/maintenance concerns. As far as we can tell, RGW currently does not provide a way to enforce a limit such as “keep only the last N versions per object key,” and existing quotas only apply at bucket/user level, not per object key. We wanted to ask: * Have others seen similar cases with very high version counts for individual keys? * How do you handle or mitigate this operationally today Any advice or shared experience would be very appreciated. Thank you, Ansgar Jazdzewski