Bug 1965314 - [RFE] client latency getting impacted after bucket reaching max size quota
Summary: [RFE] client latency getting impacted after bucket reaching max size quota
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 4.3
Assignee: Or Friedmann
QA Contact: Vidushi Mishra
Ranjini M N
URL:
Whiteboard:
Depends On: 1954392
Blocks: 1958910 2031070
TreeView+ depends on / blocked
 
Reported: 2021-05-27 12:35 UTC by Matt Benjamin (redhat)
Modified: 2022-05-05 07:53 UTC (History)
13 users (show)

Fixed In Version: ceph-14.2.21-8.el8cp, ceph-14.2.21-8.el7cp
Doc Type: Bug Fix
Doc Text:
.The `rgw_bucket_quota_soft_threshold` parameter is disabled Previously, the Ceph Object Gateway fetched utilization information from the bucket index if the cached utilization reached `rgw_bucket_quota_soft_threshold` causing high operations on the bucket index and slower requests. This release removes the `rgw_bucket_quota_soft_threshold` parameter and uses the cached stats resulting in better performance even if the quota limit is almost reached.
Clone Of: 1954392
Environment:
Last Closed: 2022-05-05 07:53:20 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ceph ceph pull 41495 0 None None None 2021-08-03 15:45:09 UTC
Red Hat Issue Tracker RHCEPH-1355 0 None None None 2021-08-30 16:59:03 UTC
Red Hat Product Errata RHSA-2022:1716 0 None None None 2022-05-05 07:53:39 UTC

Comment 12 errata-xmlrpc 2022-05-05 07:53:20 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 (Moderate: Red Hat Ceph Storage 4.3 Security and Bug Fix update), 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-2022:1716
Note You need to log in before you can comment on or make changes to this bug.