Actions
Bug #53309
closedchange pg_autoscale profile to scale-up by default
Status:
Resolved
Priority:
High
Assignee:
Category:
pg_autoscaler module
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
The autoscale profile will remain scale-up by default until we implement a feature that allows us to impose a limit on the maximum number of PGs in the device_health_metrics or. mgr pool. The reason for this is because scale-down mode can sometimes scale the PGs too large and might run into issues such as failed pool creation due to exceeding mon_max_pg_per_osd limit and etc
Updated by Neha Ojha over 2 years ago
- Tracker changed from Fix to Bug
- Project changed from Ceph to mgr
- Category set to pg_autoscaler module
- Regression set to No
- Severity set to 3 - minor
Updated by Kamoltat (Junior) Sirivadhna over 2 years ago
- Pull request ID set to 43999
Updated by Neha Ojha over 2 years ago
- Status changed from New to Fix Under Review
- Backport set to pacific
Updated by Neha Ojha over 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot over 2 years ago
- Copied to Backport #53348: pacific: change pg_autoscale profile to scale-up by default added
Updated by Neha Ojha over 2 years ago
- Status changed from Pending Backport to Resolved
Actions