Bug 1717135
Summary: | S3 client timed out in RGW - listing the large buckets having ~14 million objects with 256 bucket index shards | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
Component: | RGW | Assignee: | Marcus Watts <mwatts> |
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
Severity: | high | Docs Contact: | Aron Gunn <agunn> |
Priority: | high | ||
Version: | 3.2 | CC: | agunn, assingh, cbodley, ceph-eng-bugs, ceph-qe-bugs, fweimer, ivancich, jbrier, jquinn, kbader, kjosy, kurathod, mamccoma, mbenjamin, mhackett, mmanjuna, mnovak, mwatts, sweil, tchandra, tserlin |
Target Milestone: | rc | ||
Target Release: | 3.3 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-21 15:11:09 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1726135 |
Description
Vikhyat Umrao
2019-06-04 18:46:08 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 |