Bug 1717135 - S3 client timed out in RGW - listing the large buckets having ~14 million objects with 256 bucket index shards
Summary: S3 client timed out in RGW - listing the large buckets having ~14 million obj...
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
high
high
Target Milestone: rc
: 3.3
Assignee: Marcus Watts
QA Contact: Tejas
Aron Gunn
URL:
Whiteboard:
Depends On:
Blocks: 1726135
TreeView+ depends on / blocked
 
Reported: 2019-06-04 18:46 UTC by Vikhyat Umrao
Modified: 2019-11-11 09:21 UTC (History)
21 users (show)

Fixed In Version: RHEL: ceph-12.2.12-38.el7cp Ubuntu: ceph_12.2.12-35redhat1
Doc Type: Bug Fix
Doc Text:
.A performance decrease when listing buckets with large object counts due to a regression was resolved RADOS Gateway introduced a peformance regression as a byproduct of changes in {product} 3.2z2, which added support for multicharacter delimiters. This could cause S3 clients to time out. The regression has been fixed, restoring the original performance when listing buckets with large object counts. S3 clients no longer time out due to this issue.
Clone Of:
Environment:
Last Closed: 2019-08-21 15:11:09 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:2538 0 None None None 2019-08-21 15:11:26 UTC

Description Vikhyat Umrao 2019-06-04 18:46:08 UTC 
Description of problem:
S3 client timed out in RGW - large buckets having ~14 million objects with 256 bucket index shards


Version-Release number of selected component (if applicable):
RHCS 3.2.z2 - 12.2.8-128.el7cp

How reproducible:
At customer site always.
Comment 109 errata-xmlrpc 2019-08-21 15:11:09 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, 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-2019:2538
Note You need to log in before you can comment on or make changes to this bug.