<div dir="ltr">Dmitri the recommendation from redhat is likely because it is recommended to have the data stripes be a power of two otherwise there is a performance penalty. <br></div><div class="gmail_extra"><br><div class="gmail_quote">On 31 July 2017 at 14:28, Dmitri Chebotarov <span dir="ltr"><<a href="mailto:4dimach@gmail.com" target="_blank">4dimach@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi</div><div><br></div><div>I'm looking for an advise to configure a dispersed volume. </div><div>I have 12 servers and would like to use 10:2 ratio.</div><div><br></div><div>Yet RH recommends 8:3 or 8:4 in this case: </div><div><br></div><a href="https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/chap-Recommended-Configuration_Dispersed.html" target="_blank">https://access.redhat.com/<wbr>documentation/en-US/Red_Hat_<wbr>Storage/3.1/html/<wbr>Administration_Guide/chap-<wbr>Recommended-Configuration_<wbr>Dispersed.html</a><br><div><br></div><div>My goal is to create 2PT volume, and going with 10:2 vs 8:3/4 saves a few bricks. With 10:2 I'll use 312 8TB bricks and with 8:3 it's 396 8TB bricks (36 8:3 slices to evenly distribute between all servers/bricks)</div><div><br></div><div>As I see it 8:3/4 vs 10:2 gives more data redundancy (3 servers vs 2 servers can be offline), but is critical with 12 nodes? Nodes are new and under warranty, it's unlikely I will lose 3 servers at the same time (10:2 goes offline). Or should I follow RH recommended configuration and use 8:3/4? </div><div><br></div><div>Thank you.</div></div>
<br>______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>