I realised this operation with no impact using this way :
1- I duplicated the rule used by my pools and give it the number of the new
corresponding rule in the new crushmap
2- I set the noout
3- I set the new crushmap
4- I unset the noout
Everything was fine (i already had set max_backfill and ot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm not aware of a way of slowing things down other then modifying
osd_max_backfills, osd_backfill_scan_{min,max}, and
osd_recovery_max_activate as mentioned in [1]. The nature of injecting
a new CRUSH map us usually the result of several changes and
Hi,
I need to import a new crushmap in production (the old one is the default
one) to define two datacenters and to isolate SSD from SATA disk. What is
the best way to do this without starting an hurricane on the platform ?
Till now, i was just using hosts (SATA OSD) on one datacenter with the
de