Bug 2325408 - [RGW] HEAD on bucket shall not traverse all bucket index shards [NEEDINFO]
Summary: [RGW] HEAD on bucket shall not traverse all bucket index shards
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: 8.1
Assignee: J. Eric Ivancich
QA Contact: sohan singh
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2351689
TreeView+ depends on / blocked
 
Reported: 2024-11-12 09:19 UTC by Harald Klein
Modified: 2025-06-04 12:03 UTC (History)
8 users (show)

Fixed In Version: ceph-19.2.1-113.el9cp
Doc Type: Enhancement
Doc Text:
.HeadBucket requests are now less resource intensive Previously, all HeadBucket requests required querying all the shards to assemble statistics, which made the requests resource intensive operations. With this enhancement, the HeadBucket API now reports the `X-RGW-Bytes-Used` and `X-RGW-Object-Count` headers only when the `read-stats` query string is explicitly included in the API request. As a result, HeadBucket requests are now less resource intensive but results received, when specified.
Clone Of:
Environment:
Last Closed:
Embargoed:
mbenjamin: needinfo? (ivancich)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-10223 0 None None None 2024-11-12 09:49:41 UTC

Description Harald Klein 2024-11-12 09:19:29 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.