Bug 1813349
Summary: | rgw: raise default bucket-index sharding to 11 (OCS, Perf) | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Matt Benjamin (redhat) <mbenjamin> |
Component: | RGW | Assignee: | Matt Benjamin (redhat) <mbenjamin> |
Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
Severity: | high | Docs Contact: | Aron Gunn <agunn> |
Priority: | medium | ||
Version: | 4.0 | CC: | agunn, cbodley, ceph-eng-bugs, ceph-qe-bugs, hyelloji, kbader, mbenjamin, sweil, tserlin, vimishra |
Target Milestone: | rc | Flags: | hyelloji:
needinfo-
|
Target Release: | 4.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-14.2.8-4.el8, ceph-14.2.8-4.el7 | Doc Type: | Enhancement |
Doc Text: |
.Ceph Object Gateway's default bucket-index shards increased to 11
The default number of bucket-index shards for new buckets has been increased, from 1 to 11.
This increases the amount of write throughput for small buckets and delays the onset of dynamic resharding.
This change only affects new deployments and zones.
For existing deployments, you can change this default value using the `radosgw-admin zonegroup modify --bucket-index-max-shards=11` command.
If the zonegroup is part of a realm, the change must be committed with `radosgw-admin period update --commit` command.
If a commit is not done, then the change will take effect until after the Ceph Object Gateways are restarted.
NOTE: After an upgrade, the new default value has to be increased manually, but on new {storage-product} 4.1 deployments the new default value is set automatically.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-19 17:33:05 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: | 1816167 |
Description
Matt Benjamin (redhat)
2020-03-13 14:58:43 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-2020:2231 |