Bug #49364
closed
pg_autoscaler causes device_health_metrics pool to use 128 pgs preventing rgw from being deployed
Added by Daniel Pivonka about 3 years ago.
Updated over 2 years ago.
Backport:
pacific, octopus
Description
when trying to deploy rgw on a master or pacific cluster the device_health_metrics pool is using 128 pgs. when you try to setup a rgw service it will attempt to create pools but it fails because there are not enough pgs left to stay under the mon_max_pg_per_osd limit.
this could be the result of changes to the pg autoscaler https://github.com/ceph/ceph/pull/38805 https://github.com/ceph/ceph/pull/39248
Files
- Project changed from Ceph to mgr
- Subject changed from device_health_metrics pool is using 128 pgs preventing rgw from being deployed to pg_autoscaler causes device_health_metrics pool to use 128 pgs preventing rgw from being deployed
- Priority changed from Normal to Urgent
- Assignee set to Kamoltat (Junior) Sirivadhna
- Blocks Bug #49435: cephadm: rgw not getting deployed due to HEALTH_WARN added
- Backport set to pacific, octopus, nautilus
- Severity changed from 3 - minor to 1 - critical
Not be able to deploy/use any Ceph service is a critical issue
- Status changed from New to Fix Under Review
- Pull request ID set to 39833
- Blocks deleted (Bug #49435: cephadm: rgw not getting deployed due to HEALTH_WARN)
- Status changed from Fix Under Review to Pending Backport
- Backport changed from pacific, octopus, nautilus to pacific, octopus
- Copied to Backport #52519: pacific: pg_autoscaler causes device_health_metrics pool to use 128 pgs preventing rgw from being deployed added
- Copied to Backport #52520: octopus: pg_autoscaler causes device_health_metrics pool to use 128 pgs preventing rgw from being deployed added
- Status changed from Pending Backport to Resolved
- Pull request ID changed from 39833 to 43999
Also available in: Atom
PDF