That's been already increased to 4. Istvan Szabo Senior Infrastructure Engineer --------------------------------------------------- Agoda Services Co., Ltd. e: [email protected] ---------------------------------------------------
-----Original Message----- From: Eugen Block <[email protected]> Sent: Wednesday, September 22, 2021 2:51 PM To: [email protected] Subject: [ceph-users] Re: Modify pgp number after pg_num increased Email received from the internet. If in doubt, don't click any link nor open any attachment ! ________________________________ Hi, IIRC in a different thread you pasted your max-backfill config and it was the lowest possible value (1), right? That's why your backfill is slow. Zitat von "Szabo, Istvan (Agoda)" <[email protected]>: > Hi, > > By default in the newer versions of ceph when you increase the pg_num > the cluster will start to increase the pgp_num slowly up to the value > of the pg_num. > I've increased the ec-code data pool from 32 to 128 but 1 node has > been added to the cluster and it's very slow. > > pool 28 'hkg.rgw.buckets.data' erasure profile data-ec size 6 min_size > 5 crush_rule 1 object_hash rjenkins pg_num 128 pgp_num 55 > pgp_num_target 128 autoscale_mode warn last_change 16443 lfor > 0/0/14828 fl > ags hashpspool stripe_width 16384 application rgw > > At the moment there has been done 55 out of the 128 pg. > Is it safe to set the pgp_num at this stage to 64 and wait until the > data will be rebalanced to the newly added node? > > Thank you > _______________________________________________ > ceph-users mailing list -- [email protected] To unsubscribe send an > email to [email protected] _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ ceph-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
