Bug 1997332
Summary: | [RFE] Global on/off flag for PG autoscale feature | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vikhyat Umrao <vumrao> |
Component: | RADOS | Assignee: | Kamoltat (Junior) Sirivadhna <ksirivad> |
Status: | CLOSED ERRATA | QA Contact: | Pawan <pdhiran> |
Severity: | medium | Docs Contact: | Ranjini M N <rmandyam> |
Priority: | unspecified | ||
Version: | 5.0 | CC: | agunn, akupczyk, bhubbard, ceph-eng-bugs, ksirivad, mmurthy, nojha, pdhiran, rmandyam, rzarzyns, sseshasa, tserlin, vumrao |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | 5.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-16.2.7-39.el8cp | Doc Type: | Enhancement |
Doc Text: |
.Use the `noautoscale` flag to manage the PG autoscaler
With this release, `pg_autoscaler` can be turned `on` or `off` globally using the `noautoscale` flag.
This flag is set to `off` by default.
When this flag is set, then all the pools have `pg_autoscale_mode` as `off`
For more information, see the link:{storage-strategies-guide}#manually-updating-autoscale-profile[_Manually updating autoscale profile_] section in the _{storage-product} Storage Strategies Guide_.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-04-04 10:21:20 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: | 2031073 |
Description
Vikhyat Umrao
2021-08-25 01:36:30 UTC
Sure thing! Hi, Yep, the doc text looks good. Thank you, 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 5.1 Security, Enhancement, 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:1174 |