Replace OSD with larger

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

What is the recommended procedure for replacing an osd with a larger osd
in a safe and efficient manner, i.e. whilst maintaining redundancy and
causing the least data movement?

Would this be a matter of adding the new osd into the crush map whilst
reducing the weight of the old osd to zero, then once the dust has
settled, removing the old osd from the crush map?

Assuming that's the general process, if replacing multiple osds with
larger ones, is it safer and/or more efficient to do this sequentially
(i.e. add new1 and set old1 weight to zero, wait for movement to finish,
add new2 and set old2 to weight to zero, wait etc.) or do them all at once?

It's my understanding that even if an osd is unused, removing it
from the crush map can change placement calculations thus
causing data movement. Is this the case? If so, this would
indicate that, even if replacing multiple osds is better done
sequentially, it would still be more efficient to remove all the
old osds in one go at the end, correct?

(I'm currently on Dumpling, if it matters.)

Cheers,

Chris
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux