<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 15, 2017 at 5:48 PM, Alex K <span dir="ltr"><<a href="mailto:rightkicktech@gmail.com" target="_blank">rightkicktech@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><div>In the replica 3 + 1 arbiter does this mean that if I loose the two nodes having the normal volumes and left only with the node that has the arbiter volume, I loose all data?<br></div></div></div></blockquote><div><br></div><div>Yes!<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><br></div>Thanx, <br></div>Alex<br></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 15, 2017 at 11:25 AM, Kasturi Narra <span dir="ltr"><<a href="mailto:knarra@redhat.com" target="_blank">knarra@redhat.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">Hi ,<div><br></div><div> yes, you are right. Since arbiter brick has only metadata and data for the vm has to be served from one of the other two replicas, read is slow. </div><div><br></div><div> Arbiter is a special subset of replica 3 volumes and is aimed at preventing split-brains and providing same consistency as a normal replica 3 volume with out consuming 3x space. You could use replica 3 and no issues with that.</div><div><br></div><div>Thanks</div><div>kasturi</div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-721820785018703641h5">On Fri, Sep 15, 2017 at 12:41 PM, Abi Askushi <span dir="ltr"><<a href="mailto:rightkicktech@gmail.com" target="_blank">rightkicktech@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-721820785018703641h5"><div dir="ltr"><div><div><div><div><div>Hi all, <br><br></div>I see in the ovirt guides that a gluster volume replica 3 with 1 arbiter is recommended. <br></div>Why not simple replica 3? Is it due to the higher replication data that would cause performance issues?<br><br></div>What I am observing is that a VM running on the server which has the arbiter brick has slower read performance then when the same VM runs on another server with a normal brick. Has anyone observed this? Is it because the arbiter does not have the real data on it?<br><br></div>Thanx,<br></div>Alex<br></div>
<br></div></div>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org" target="_blank">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/mailman<wbr>/listinfo/users</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.ovirt.org/<wbr>mailman/listinfo/users</a><br>
<br></blockquote></div><br></div></div>