Hi, I understand this warning, but not why it was not there before. We have set the pg_num on 4096 months (maybe even a year...) ago but forgot the pgp_num. I think with current releases this should not have happened, but we have it __ (probably while we still were running Mimic). So that's the odd part.
Met vriendelijke groet, Kind Regards, Maarten van Ingen Specialist |SURF |maarten.vanin...@surf.nl <mailto:voornaam.achtern...@surf.nl>| T +31 30 88 787 3000 |M +31 6 19 03 90 19| SURF <http://www.surf.nl/> is the collaborative organisation for ICT in Dutch education and research Op 15-02-2022 09:40 heeft Janne Johansson <icepic...@gmail.com> geschreven: Den tis 15 feb. 2022 kl 08:56 skrev Maarten van Ingen <maarten.vanin...@surf.nl>: > 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@ceph.io To unsubscribe send an email to ceph-users-le...@ceph.io
