<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/30/2016 11:40 AM, Atin Mukherjee
wrote:<br>
</div>
<blockquote
cite="mid:CAGNCGH2jMqCEnJMfOgF-C7JGUd08UxVs58-QqrwFJEPgTsOVwQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Currently on a two node set up, if node B goes down and
node A is rebooted brick process(es) on node A doesn't come up
to avoid split brains. </div>
</div>
</blockquote>
<br>
This has always been the case. A patch I had sent quite some time
back (<a class="moz-txt-link-freetext" href="http://review.gluster.org/#/c/8034/">http://review.gluster.org/#/c/8034/</a>) was eventually abandoned,
I think `volume start force` should suffice instead of adding checks
in code.<br>
-Ravi<br>
<br>
<blockquote
cite="mid:CAGNCGH2jMqCEnJMfOgF-C7JGUd08UxVs58-QqrwFJEPgTsOVwQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>However we have had concerns/bugs from different gluster
users on the availability with this configuration. So we can
solve this issue by starting the brick process(es) if quorum
is not enabled. If quorum is enabled we'd not. Although quorum
option really doesn't make sense in a two node cluster, but we
can leverage this option to get rid of this specific
situation. <br>
<br>
</div>
<div>I'd like to know your feedback on this and then I push a
patch right away.<br>
<br>
</div>
<div>~Atin<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-users">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>