<div dir="ltr"><div>Hello Ravi,</div><div><br></div><div>Thank you for the explanation! Now it is clear</div><div><br></div><div>Best regards,</div><div>Alexandr</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 26, 2016 at 3:07 PM, Ravishankar N <span dir="ltr"><<a href="mailto:ravishankar@redhat.com" target="_blank">ravishankar@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 bgcolor="#FFFFFF" text="#000000"><span class="">
<div class="m_4911789120954705424moz-cite-prefix">On 11/26/2016 04:54 PM, Alexandr
Porunov wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hello,</div>
<div><br>
</div>
<div>I am using GlusterFS 3.8.5. I wonder to know when to use
Arbiter volumes and quorum options in GlusterFS and what
difference between them?</div>
<div><br>
</div>
<div>I tried to achive a split-brain in a replicated voulume 3
but couldn't. Does GlusterFS manage split-brain situations
automaticaly?</div>
<div><br>
</div>
<div>I tried following:</div>
<div>node1, node2, node3 is the nodes with a replicated volume.</div>
<div>I have created a network crash between node1 and node3 but
node1 and node3 still can speak with node2. When I write a
file to node1 it automatically creates on node2 and node3.
When I write a file to node3 it automaticaly creates on node2
and node1.</div>
<div><br>
</div>
<div>I tried to crash node1 then write to node3 and then crash a
node3 and recover node1. Still it works just fine. I tried to
crash two nodes and then write to the healthy node and it
doesn't work. After I have run one more node it started work.</div>
<div><br>
</div>
<div>Is it possible to achive a split-brain in a GlusterFS
cluster 3.8.5? If yes then how and what options we have to set
to prevent split-brain? If no then why do we need an arbiter
and quorum options?</div>
<div><br>
</div>
</div>
</blockquote>
<br></span>
Split-brains are possible in replica-2 volumes. They don't occur in
replica-3 volumes or arbiter-volumes. Client-quorum is enabled and
set to 'auto' when you create replica-3 or arbiter vols. You're not
supposed to change it. Arbiter vols can be used if you want to avoid
split-brains but don't want to invest in a 3rd data brick for
replica-3. Of course, the availability of arbiter is less compared
to replica-3 because we don't store the actual file content in the
3rd (arbiter) brick.<br>
<br>
You can find more information @
<a class="m_4911789120954705424moz-txt-link-freetext" href="http://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/" target="_blank">http://gluster.readthedocs.io/<wbr>en/latest/Administrator%<wbr>20Guide/arbiter-volumes-and-<wbr>quorum/</a>
and
<a class="m_4911789120954705424moz-txt-link-freetext" href="http://events.linuxfoundation.org/sites/events/files/slides/glusterfs-arbiter-VAULT-2016.pdf" target="_blank">http://events.linuxfoundation.<wbr>org/sites/events/files/slides/<wbr>glusterfs-arbiter-VAULT-2016.<wbr>pdf</a><br>
<br>
Regards,<br>
Ravi<br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div>Sincerely,</div>
<div>Alexandr</div>
</div>
<br>
<fieldset class="m_4911789120954705424mimeAttachmentHeader"></fieldset>
<br>
<pre>______________________________<wbr>_________________
Gluster-users mailing list
<a class="m_4911789120954705424moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a class="m_4911789120954705424moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-users</a></pre>
</blockquote>
<p><br>
</p>
</div>
</blockquote></div><br></div>