Den tis 15 feb. 2022 kl 08:56 skrev Maarten van Ingen <maarten.vaningen@xxxxxxx>: > Hi, > After enabling the balancer (and set to upmap) on our environment it’s time to get the pgp_num on one of the pools on par with the pg_num. > This pool has pg_num set to 4096 and pgp_num to 2048 (by our mistake). > I just set the pgp_num to 2248 to keep data movement in check. > Oddly enough I see it’s only increased to 2108, also it’s odd we now get this health warning: 1 pools have pg_num > pgp_num, which we haven’t seen before… That warning is 100% correct and expected when you set pg_num to <large number> and the pgp_num gradually moves towards this larger target number. In itself, nothing to worry about, this is exactly what ceph -s should be saying until pgp_num also becomes 4096. More or less a warning to say "don't forget to make bumps of pgp_num until it matches pg_num". -- May the most significant bit of your life be positive. _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |