Editing Crush Map to fix osd_crush_chooseleaf_type = 0

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

 



Hi all,

We have a 12 OSD node cluster in which I just recently found out that 'osd_crush_chooseleaf_type  = 0' made it's way into our ceph.conf file, probably from previous testing. I believe this is the reason a recent maintenance on an OSD node caused data to stop flowing. In researching how to fix this, I just wanted to confirm a few things and see if anybody who has done this before has any perspective or things to look out for.

1) I believe the correct way to fix this is by following the 5 step method in the documentation; Get, Decompile, Edit, Recompile, Set. Is that correct and is the line I should change 'choose_firstn' to 'chooseleaf_firstn'? Do I only make this change on 1 mon and it will propagate it to all other mons and osds?

2) Does the process start immediately following the setcrushmap command? 

3) Any files to backup prior to this operation? This is production data so we can not have any data loss. 

4) Any other notes/things to be aware of?

Thank you
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx



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


  Powered by Linux