> the option is now called 'mon_max_pg_per_osd'.
>
> this was originally slated for v12.2.1 where it was erroneously
> mentioned in the release notes[1] despite note being part of the
> release (I remember asking for updated/fixed release notes after 12.2.1,
> seems like that never happened?). now
> Why are you OK with this? A high amount of PGs can cause serious peering
> issues. OSDs might eat up a lot of memory and CPU after a reboot or such.
>
> Wido
Mainly because there was no warning at all in v12.2.1 and it just
appeared after upgrading to v12.2.2. Besides,its not a "too high" numb
Hello,
I have upgraded from v12.2.1 to v12.2.2 and now a warning shows using
"ceph status":
---
# ceph status
cluster:
id:
health: HEALTH_WARN
too many PGs per OSD (208 > max 200)
---
I'm ok with the amount of PGs, so I'm trying to increase the max PGs.
I've tried addin