Description of problem: A HEAD request on a bucket does trigger traversal of all bucket index shards Version-Release number of selected component (if applicable): RHCS 7.1 How reproducible: HEAD request on /bucketname Steps to Reproduce: 1. HEAD request on bucket 2. watch index shard rados operations Actual results: High pressure on OMAP Expected results: As the response body is suppressed in the HEAD request and the aim likely is to check existence, it would be preferred if the index shard traversal could be skipped for such request. This would reduce the performance impact on large buckets. Additional info: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html This is also used e.g. by jclouds in the bucketExists() method.
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 (Important: Red Hat Ceph Storage 8.1 security, bug fix, and enhancement updates), 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/RHSA-2025:9775