Hi,
consider yourself lucky that you haven't had a host failure. But I
would not draw the wrong conclusions here and change the
failure-domain based on luck.
In our production cluster we have an EC pool for archive purposes, it
all went well for quite some time and last Sunday one of the hosts
suddenly failed, we're still investigating the root cause. Our
failure-domain is host and I'm glad that we chose a suitable EC
profile for that, the cluster is healthy.
Also what is the "optimal" like 12:3 or ?
You should evaluate that the other way around. What are your specific
requirements regarding resiliency (how many hosts can fail at the same
time without data loss)? How many hosts are available? Are you
planning to expand in the near future? Based on this evaluation you
can conclude a few options and choose the best for your requirements.
Regards,
Eugen
Zitat von "Szabo, Istvan (Agoda)" <Istvan.Szabo@xxxxxxxxx>:
Hi,
What's your take on an osd based ec-code setup? I've never been
brave enough to use OSD based crush rule because scared host failure
but in the last 4 years we have never had any host issue so I'm
thinking to change to there and use some more cost effective EC.
Also what is the "optimal" like 12:3 or ?
Thank you
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
