+1 for swap-bucket, we've been using that as well successfully.
What we also sometimes do, especially when time is a bit more
critical, is to purge OSDs of an entire host (we also did this with
two hosts at the same time due to high resiliency) and then let Ceph
recover. But I generally don't recommend that to unexperienced
operators.
Zitat von Harald Staub via ceph-users <[email protected]>:
Not recently, but a few years ago, I used the "Whole host
replacement" using "swap-bucket":
https://docs.ceph.com/en/latest/rados/operations/bluestore-migration/
This worked really nicely. With source and destination about the
same host CRUSH weight, most PGs are moved directly from source to
destination. So also the copy speed was more or less the same most
of the time.
Cheers,
Harry
On 4/28/26 11:08, Denis Polom via ceph-users wrote:
you can control max_backfills and some others if you set
osd_mclock_override_recovery_settings to true
On 4/28/26 10:57, Janne Johansson via ceph-users wrote:
Another approach is to set the flags, destroy the OSDs on a
single host, redeploy them, set your backfill/recovery throttles
down to 1, and unset the flags.
This is harder with mclock right? With wpq you can still control
max_backfills, but not with mclock unless I am mistaken.
_______________________________________________
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]
