<div dir="ltr">this all makes sense and sounds a bit like a solr setup :-)<div><br></div><div>I have now added the third node as a peer </div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt">sudo gluster peer probe gs3</span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt">That indeed allow me to mount the share manually on node2 even if node1 is down. </span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt">BUT: It does not mount on reboot! It only successfully mounts if node1 is up. I need to do a manual: sudo mount -a</span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt"><br></span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt">Is there a particular reason for this, or is it a misconfiguration?</span></div><div><span style="color:rgb(51,51,51);font-family:Courier;font-size:10.5pt"><br></span></div>
<span style="font-size:10.5pt;font-family:Courier;color:rgb(51,51,51)"> <br></span></div><div class="gmail_extra"><br><div class="gmail_quote">2015-08-31 21:01 GMT+02:00 Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On 08/31/2015 10:41 AM, Vijay Bellur wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Monday 31 August 2015 10:42 PM, Atin Mukherjee wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
> 2. Server2 dies. Server1 has to reboot.<br>
><br>
> In this case the service stays down. It is inpossible to remount the<br>
share without Server1. This is not acceptable for a High Availability<br>
System and I believe also not intended, but a misconfiguration or bug.<br>
This is exactly what I gave as an example in the thread (please read<br>
again). GlusterD is not supposed to start brick process if its other<br>
counter part hasn't come up yet in a 2 node setup. The reason it has<br>
been designed in this way is to block GlusterD on operating on a volume<br>
which could be stale as the node was down and cluster was operational<br>
earlier.<br>
</blockquote>
<br>
For two node deployments, a third dummy node is recommended to ensure that quorum is maintained when one of the nodes is down.<br>
<br>
Regards,<br>
Vijay<br>
</blockquote>
<br></div></div>
Have the settings changed to enable server quorum by default?<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br>
</div></div></blockquote></div><br></div>