Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
This project is now read‑only. Starting Monday, February 2, please use Jira Cloud for all bug tracking management.

Bug 2365106

Summary: [rgw] high memory usage of radosgw process when performing multi-part PUT workload at overload (when returning 503s)
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Mark Kogan <mkogan>
Component: RGWAssignee: Mark Kogan <mkogan>
Status: CLOSED ERRATA QA Contact: Madhavi Kasturi <mkasturi>
Severity: medium Docs Contact: Rivka Pollack <rpollack>
Priority: unspecified    
Version: 7.1CC: ceph-eng-bugs, cephqe-warriors, dwalveka, mkasturi, rpollack, tserlin, vereddy
Target Milestone: ---   
Target Release: 7.1z5   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-18.2.1-330.el9cp Doc Type: Bug Fix
Doc Text:
New support for handling Head and GetObject operations with partNumber Previously, when performing more than rgw_max_concurrent_requests concurrent multipart PUT operations, the radosgw process exhibited higher than expected memory usage. This issue occurred when using a client that supported HEAD/GET requests for individual parts of a completed multipart upload with the partNumber query parameter. With this fix, support for handling Head and GetObject operations with the partNumber parameter is added, ensuring that memory usage under this workload remains at the expected size.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-23 02:52:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 9 errata-xmlrpc 2025-06-23 02:52:14 UTC 
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 (Red Hat Ceph Storage 7.1 security and bug fix 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/RHBA-2025:9335