2-Layer CRUSH Map Rule?

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

 



Hi Everybody (Hi Dr. Nick),

TL/DR: Is is possible to have a "2-Layer" Crush Map?

I think it is (although I'm not sure about how to set it up).

My issue is that we're using 4-2 Erasure coding on our OSDs, with 7-OSDs per OSD-Node (yes, the Cluster is handling things AOK - we're running at about 65-70% utilisation of CPU, RAM, etc, so no problem there).

However, we only have 3 OSD-Nodes, and I'd like to ensure that each Node has 2 of each pool's OSDs so that if we loose a Node the other 2 can take up the slack. I know(?) that with 4-2 EC we can loose 2 out of the 6 OSDs, but I'm worried that if we loose a Node it'll take more than 2 OSDs with it, rendering us "stuffed" (stuffed: a technical term which is used as a substitute for a four-letter word rhyming with "truck") 😁

Anyone have any pointers?

Cheers

Dulux-Oz

_______________________________________________
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