Re: OSD disk replacement best practise

[Smart Weblications GmbH - Florian Wiessner <f.wiessner-o+pLhCRhXQuTURD7UP6EnqXJknND6eY5@public.gmane.org>]

Am 14.08.2014 13:29, schrieb Guang Yang:
> Hi cephers,
> Most recently I am drafting the run books for OSD disk replacement, I think the rule of thumb is to reduce data migration (recover/backfill), and I thought the following procedure should achieve the purpose:
>   1. ceph osd out osd.XXX (mark it out to trigger data migration)
>   2. ceph osd rm osd.XXX
>   3. ceph auth rm osd.XXX
>   4. provision a new OSD which will take XXX as the OSD id and migrate data back.
> 
> With the above procedure, the crush weight of the host never changed so that we can limit the data migration only for those which are neccesary.
> 
> Does it make sense?
> 

Looks sane to me, and i remember that i did it that way a few times.


-- 

Mit freundlichen Grüßen,

Florian Wiessner

Smart Weblications GmbH
Martinsberger Str. 1
D-95119 Naila

fon.: +49 9282 9638 200
fax.: +49 9282 9638 205
24/7: +49 900 144 000 00 - 0,99 EUR/Min*
http://www.smart-weblications.de

--
Sitz der Gesellschaft: Naila
Geschäftsführer: Florian Wiessner
HRB-Nr.: HRB 3840 Amtsgericht Hof
*aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz