Hi, During Hosted Engine setup question about glusterfs volume is being asked because you have setup the volumes yourself. If cockpit+gdeploy plugin would be have been used then that would have automatically detected glusterfs replica 3 volume created during Hosted Engine deployment and this question would not have been asked. During new storage domain creation when glusterfs is selected there is a feature called 'use managed gluster volumes' and upon checking this all glusterfs volumes managed will be listed and you could choose the volume of your choice from the dropdown list. There is a conf file called /etc/hosted-engine/hosted-engine.conf where there is a parameter called backup-volfile-servers="h1:h2" and if one of the gluster node goes down engine uses this parameter to provide ha / failover. Hope this helps !! Thanks kasturi On Wed, Aug 30, 2017 at 8:09 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

yes, right. What you can do is edit the hosted-engine.conf file and there is a parameter as shown below [1] and replace h2 and h3 with your second and third storage servers. Then you will need to restart ovirt-ha-agent and ovirt-ha-broker services in all the nodes . [1] 'mnt_options=backup-volfile-servers=<h2>:<h3>' On Thu, Aug 31, 2017 at 5:54 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

Typo..."Set it up and then failed that **HOST**" And upon that host going down, the storage domain went down. I only have hosted storage domain and this new one - is this why the DC went down and no SPM could be elected? I dont recall this working this way in early 4.0 or 3.6 On Thu, Aug 31, 2017 at 3:30 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

If gluster drops in quorum so that it has less votes than it should it will stop file operations until quorum is back to normal.If i rember it right you need two bricks to write for quorum to be met and that the arbiter only is a vote to avoid split brain. Basically what you have is a raid5 solution without a spare. And when one disk dies it will run in degraded mode. And some raid systems will stop the raid until you have removed the disk or forced it to run anyway.  You can read up on it here: https://gluster.readthedocs.io/en/latest/Ad ministrator%20Guide/arbiter-volumes-and-quorum/ /JohanOn Thu, 2017-08-31 at 22:33 -0700, Jim Kusznir wrote:

@ Jim - you have only two data volumes and lost quorum. Arbitrator only stores metadata, no actual files. So yes, you were running in degraded mode so some operations were hindered. @ Sahina - Yes, this actually worked fine for me once I did that. However, the issue I am still facing, is when I go to create a new gluster storage domain (replica 3, hyperconverged) and I tell it "Host to use" and I select that host. If I fail that host, all VMs halt. I do not recall this in 3.6 or early 4.0. This to me makes it seem like this is "pinning" a node to a volume and vice versa like you could, for instance, for a singular hyperconverged to ex: export a local disk via NFS and then mount it via ovirt domain. But of course, this has its caveats. To that end, I am using gluster replica 3, when configuring it I say "host to use: " node 1, then in the connection details I give it node1:/data. I fail node1, all VMs halt. Did I miss something? On Fri, Sep 1, 2017 at 2:13 AM, Sahina Bose <sabose(a)redhat.com&gt; wrote:

Are you referring to "Mount Options" - > http://i.imgur.com/bYfbyzz.png Then no, but that would explain why it wasnt working :-). I guess I had a silly assumption that oVirt would have detected it and automatically taken up the redundancy that was configured inside the replica set / brick detection. I will test and let you know Thanks! On Fri, Sep 1, 2017 at 8:52 AM, Kasturi Narra <knarra(a)redhat.com&gt; wrote:

Huh...Ok., how do I convert the arbitrar to full replica, then? I was misinformed when I created this setup. I thought the arbitrator held enough metadata that it could validate or refudiate any one replica (kinda like the parity drive for a RAID-4 array). I was also under the impression that one replica + Arbitrator is enough to keep the array online and functional. --Jim On Fri, Sep 1, 2017 at 5:22 AM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

@Kasturi - Looks good now. Cluster showed down for a moment but VM's stayed up in their appropriate places. Thanks! < Anyone on this list please feel free to correct my response to Jim if its wrong> @ Jim - If you can share your gluster volume info / status I can confirm (to the best of my knowledge). From my understanding, If you setup the volume with something like 'gluster volume set <vol> group virt' this will configure some quorum options as well, Ex: http://i.imgur.com/Mya4N5o.png While, yes, you are configured for arbiter node you're still losing quorum by dropping from 2 -> 1. You would need 4 node with 1 being arbiter to configure quorum which is in effect 3 writable nodes and 1 arbiter. If one gluster node drops, you still have 2 up. Although in this case, you probably wouldnt need arbiter at all If you are configured, you can drop quorum settings and just let arbiter run since you're not using arbiter node in your VM cluster part (I believe), just storage cluster part. When using quorum, you need > 50% of the cluster being up at one time. Since you have 3 nodes with 1 arbiter, you're actually losing 1/2 which == 50 which == degraded / hindered gluster Again, this is to the best of my knowledge based on other quorum backed software....and this is what I understand from testing with gluster and ovirt thus far On Fri, Sep 1, 2017 at 11:53 AM, Jim Kusznir <jim(a)palousetech.com&gt; wrote:

I'm now also confused as to what the point of an arbiter is / what it does / why one would use it. On Fri, Sep 1, 2017 at 11:44 AM, Jim Kusznir <jim(a)palousetech.com&gt; wrote:

On 9/1/2017 8:53 AM, Jim Kusznir wrote: I can not speak for the Ovirt implementation of Rep2+Arbiter as I've not used it, but on a standalone libvirt VM host cluster,   Arb does exactly what you want. You can lose 'one' of the two replicas and stay online. The Arb maintains quorum. Of course if you lose the second Replica before you have repaired the first failure you have completely lost your data as the Arb doesn't have that. So Rep2+Arb is not as SAFE as Rep3, however it can be faster, especially on less than 10G networks. When any node fails, Gluster will pause for 42 seconds or so (its configurable) before marking the bad node as bad. Then normal activity will resume. On most people's systems, the 'pause' (I think its a read-only event), it noticeable, but not enough to cause issue. One person has reported that his VMs went read-only during that period, but other have not reported that. -wk

So, after reading the first document twice and the 2nd link thoroughly once, I believe that the arbitrator volume should be sufficient and count for replica / split brain. EG, if any one full replica is down, and the arbitrator and the other replica is up, then it should have quorum and all should be good. I think my underlying problem has to do more with config than the replica state. That said, I did size the drive on my 3rd node planning to have an identical copy of all data on it, so I'm still not opposed to making it a full replica. Did I miss something here? Thanks! On Fri, Sep 1, 2017 at 11:59 AM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

I can confirm that I did set it up manually, and I did specify backupvol, and in the "manage domain" storage settings, I do have under mount options, backup-volfile-servers=192.168.8.12:192.168.8.13 (and this was done at initial install time). The "used managed gluster" checkbox is NOT checked, and if I check it and save settings, next time I go in it is not checked. --Jim On Fri, Sep 1, 2017 at 2:08 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

Jim - One thing I noticed is that, by accident, I used 'backupvolfile-server=node2:node3' which is apparently a supported setting. It would appear, by reading the man page of mount.glusterfs, the syntax is slightly different. not sure if my setting being different has different impacts hosted-engine.conf: # cat /etc/ovirt-hosted-engine/hosted-engine.conf | grep -i option mnt_options=backup-volfile-servers=node2:node3 And for my datatest gluster domain I have: backupvolfile-server=node2:node3 I am now curious what happens when I move everything to node1 and drop node2 To that end, will follow up with that test On Fri, Sep 1, 2017 at 7:20 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote:

Hi Jim, I looked at the gluster volume info and that looks to be fine for me. Recommended config is arbiter for data and vmstore and for engine it should be replica 3 since we would want HE to be available always. If i understand right the problem you are facing is when you shut down one of the node all the HE vms and app vms goes to paused state right ? For debugging further and to ensure that volume has been mounted using backup-volfile-servers option, you can move the storage domain to maintenance which will umount the volume , activate back which will mount it again. During this time you can check the mount command passed in vdsm logs and that should have the backup-volfile-servers option. Can you please confirm if you have ovirt-guest-agent installed on the app vms and power management enabled ? ovirt-guest-agent is required on the app vms to ensure HA functionality Thanks kasturi On Sat, Sep 2, 2017 at 2:48 AM, Jim Kusznir <jim(a)palousetech.com&gt; wrote:

This is a multi-part message in MIME format. --------------9AE8F9DB18CD3709026D88C7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit I had the very same impression. It doesn't look like that it works then. So for a fully redundant where you can loose a complete host you must have at least 3 nodes then ? Fernando On 01/09/2017 12:53, Jim Kusznir wrote: --------------9AE8F9DB18CD3709026D88C7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <p>I had the very same impression. It doesn't look like that it works then. So for a fully redundant where you can loose a complete host you must have at least 3 nodes then ?<br> </p> <p>Fernando<br> </p> <br> <div class="moz-cite-prefix">On 01/09/2017 12:53, Jim Kusznir wrote:<br> </div> <blockquote type="cite" cite="mid:CA+5-SEonfEjQ-8-5z4F2L4tenSDJq0A9=6B3Af=URp4AKYUOzQ@mail.gmail.com"> <div dir="ltr">Huh...Ok., how do I convert the arbitrar to full replica, then?  I was misinformed when I created this setup.  I thought the arbitrator held enough metadata that it could validate or refudiate  any one replica (kinda like the parity drive for a RAID-4 array).  I was also under the impression that one replica  + Arbitrator is enough to keep the array online and functional. <div><br> </div> <div>--Jim</div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Fri, Sep 1, 2017 at 5:22 AM, Charles Kozler <span dir="ltr">&lt;<a href="mailto:ckozleriii@gmail.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;ckozleriii(a)gmail.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="ltr">@ Jim - you have only two data volumes and lost quorum. Arbitrator only stores metadata, no actual files. So yes, you were running in degraded mode so some operations were hindered. <div><br> </div> <div>@ Sahina - Yes, this actually worked fine for me once I did that. However, the issue I am still facing, is when I go to create a new gluster storage domain (replica 3, hyperconverged) and I tell it "Host to use" and I select that host. If I fail that host, all VMs halt. I do not recall this in 3.6 or early 4.0. This to me makes it seem like this is "pinning" a node to a volume and vice versa like you could, for instance, for a singular hyperconverged to ex: export a local disk via NFS and then mount it via ovirt domain. But of course, this has its caveats. To that end, I am using gluster replica 3, when configuring it I say "host to use: " node 1, then in the connection details I give it node1:/data. I fail node1, all VMs halt. Did I miss something?</div> </div> <div class="HOEnZb"> <div class="h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Fri, Sep 1, 2017 at 2:13 AM, Sahina Bose <span dir="ltr">&lt;<a href="mailto:sabose@redhat.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;sabose(a)redhat.com&lt;/a&gt;&amp;gt;&lt;/span&gt; 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>To the OP question, when you set up a gluster storage domain, you need to specify backup-volfile-servers=&lt;server<wbr>2&gt;:&lt;server3&gt; where server2 and server3 also have bricks running. When server1 is down, and the volume is mounted again - server2 or server3 are queried to get the gluster volfiles.<br> <br> </div> @Jim, if this does not work, are you using 4.1.5 build with libgfapi access? If not, please provide the vdsm and gluster mount logs to analyse<br> <br> </div> If VMs go to paused state - this could mean the storage is not available. You can check "gluster volume status &lt;volname&gt;" to see if atleast 2 bricks are running.<br> </div> <div class="m_688166259021271601HOEnZb"> <div class="m_688166259021271601h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Fri, Sep 1, 2017 at 11:31 AM, Johan Bernhardsson <span dir="ltr">&lt;<a href="mailto:johan@kafit.se" target="_blank" moz-do-not-send=&quot;true&quot;&gt;johan(a)kafit.se&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div> <div>If gluster drops in quorum so that it has less votes than it should it will stop file operations until quorum is back to normal.If i rember it right you need two bricks to write for quorum to be met and that the arbiter only is a vote to avoid split brain.</div> <div><br> </div> <div><br> </div> <div>Basically what you have is a raid5 solution without a spare. And when one disk dies it will run in degraded mode. And some raid systems will stop the raid until you have removed the disk or forced it to run anyway. </div> <div><br> </div> <div>You can read up on it here: <a href="https://gluster.readthedocs.io/en/latest/Administrator%20Guide/arbiter-volumes-and-quorum/" target="_blank" moz-do-not-send="true">https://gluster.readthed<wbr>ocs.io/en/latest/Administrator<wbr>%20Guide/arbiter-volumes-and-q<wbr>uorum/</a></div> <span class="m_688166259021271601m_8337997229390174390HOEnZb"><font color="#888888"> <div><br> </div> <div>/Johan</div> </font></span> <div> <div class="m_688166259021271601m_8337997229390174390h5"> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250-x-evo-paragraph m_688166259021271601m_8337997229390174390m_-8986942953698210250-x-evo-top-signature-spacer"><br> </div> <div>On Thu, 2017-08-31 at 22:33 -0700, Jim Kusznir wrote:</div> <blockquote type="cite"> <div dir="ltr">Hi all:   <div><br> </div> <div>Sorry to hijack the thread, but I was about to start essentially the same thread.</div> <div><br> </div> <div>I have a 3 node cluster, all three are hosts and gluster nodes (replica 2 + arbitrar).  I DO have the mnt_options=backup-volfile-ser<wbr>vers= set:</div> <div><br> </div> <div> <div>storage=192.168.8.11:/engine</div> <div>mnt_options=backup-volfile-ser<wbr>vers=192.168.8.12:192.168.8.13</div> </div> <div><br> </div> <div>I had an issue today where 192.168.8.11 went down.  ALL VMs immediately paused, including the engine (all VMs were running on host2:192.168.8.12).  I couldn't get any gluster stuff working until host1 (192.168.8.11) was restored.</div> <div><br> </div> <div>What's wrong / what did I miss?</div> <div><br> </div> <div>(this was set up "manually" through the article on setting up self-hosted gluster cluster back when 4.0 was new..I've upgraded it to 4.1 since).</div> <div><br> </div> <div>Thanks!</div> <div>--Jim</div> <div><br> </div> </div> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Aug 31, 2017 at 12:31 PM, Charles Kozler <span dir="ltr">&lt;<a href="mailto:ckozleriii@gmail.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;ckozleriii(a)gmail.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote type="cite"> <div dir="ltr">Typo..."Set it up and then failed that **HOST**" <div><br> </div> <div>And upon that host going down, the storage domain went down. I only have hosted storage domain and this new one - is this why the DC went down and no SPM could be elected?</div> <div><br> </div> <div>I dont recall this working this way in early 4.0 or 3.6</div> </div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250HOEnZb"> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Aug 31, 2017 at 3:30 PM, Charles Kozler <span dir="ltr">&lt;<a href="mailto:ckozleriii@gmail.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;ckozleriii(a)gmail.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote type="cite"> <div dir="ltr">So I've tested this today and I failed a node. Specifically, I setup a glusterfs domain and selected "host to use: node1". Set it up and then failed that VM <div><br> </div> <div>However, this did not work and the datacenter went down. My engine stayed up, however, it seems configuring a domain to pin to a host to use will obviously cause it to fail</div> <div><br> </div> <div>This seems counter-intuitive to the point of glusterfs or any redundant storage. If a single host has to be tied to its function, this introduces a single point of failure</div> <div><br> </div> <div>Am I missing something obvious?</div> </div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885HOEnZb"> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Aug 31, 2017 at 9:43 AM, Kasturi Narra <span dir="ltr">&lt;<a href="mailto:knarra@redhat.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;knarra(a)redhat.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote type="cite"> <div dir="ltr">yes, right.  What you can do is edit the hosted-engine.conf file and there is a parameter as shown below [1] and replace h2 and h3 with your second and third storage servers. Then you will need to restart ovirt-ha-agent and ovirt-ha-broker services in all the nodes . <div><br> </div> <div>[1] 'mnt_options=backup-volfile-se<wbr>rvers=&lt;h2&gt;:&lt;h3&gt;' </div> </div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349HOEnZb"> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Aug 31, 2017 at 5:54 PM, Charles Kozler <span dir="ltr">&lt;<a href="mailto:ckozleriii@gmail.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;ckozleriii(a)gmail.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote type="cite"> <div dir="ltr">Hi Kasturi - <div><br> </div> <div>Thanks for feedback</div> <span> <div><br> </div> <div>&gt; <span style="font-size:12.8px">If cockpit+gdeploy plugin would be have been used then that would have automatically detected glusterfs replica 3 volume created during Hosted Engine deployment and this question would not have been asked</span></div> <div><span style="font-size:12.8px">  </span></div> </span> <div><span style="font-size:12.8px">Actually, doing hosted-engine --deploy it too also auto detects glusterfs.  I know glusterfs fuse client has the ability to failover between all nodes in cluster, but I am still curious given the fact that I see in ovirt config node1:/engine (being node1 I set it to in hosted-engine --deploy). So my concern was to ensure and find out exactly how engine works when one node goes away and the fuse client moves over to the other node in the gluster cluster</span></div> <div><span style="font-size:12.8px"><br> </span></div> <div><span style="font-size:12.8px">But you did somewhat answer my question, the answer seems to be no (as default) and I will have to use hosted-engine.conf and change the parameter as you list</span></div> <div><span style="font-size:12.8px"><br> </span></div> <div><span style="font-size:12.8px">So I need to do something manual to create HA for engine on gluster? Yes?</span></div> <div><span style="font-size:12.8px"><br> </span></div> <div><span style="font-size:12.8px">Thanks so much!</span></div> </div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349m_3449479715428376713HOEnZb"> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349m_3449479715428376713h5"> <div class="gmail_extra"><br> <div class="gmail_quote">On Thu, Aug 31, 2017 at 3:03 AM, Kasturi Narra <span dir="ltr">&lt;<a href="mailto:knarra@redhat.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;knarra(a)redhat.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> <blockquote type="cite"> <div dir="ltr">Hi, <div><br> </div> <div>   During Hosted Engine setup question about glusterfs volume is being asked because you have setup the volumes yourself. If cockpit+gdeploy plugin would be have been used then that would have automatically detected glusterfs replica 3 volume created during Hosted Engine deployment and this question would not have been asked.</div> <div><br> </div> <div>   During new storage domain creation when glusterfs is selected there is a feature called 'use managed gluster volumes' and upon checking this all glusterfs volumes managed will be listed and you could choose the volume of your choice from the dropdown list.</div> <div><br> </div> <div>    There is a conf file called /etc/hosted-engine/hosted-engi<wbr>ne.conf where there is a parameter called backup-volfile-servers="h1:h2" and if one of the gluster node goes down engine uses this parameter to provide ha / failover. </div> <div><br> </div> <div> Hope this helps !!</div> <div><br> </div> <div>Thanks</div> <div>kasturi</div> <div><br> <div><br> </div> </div> </div> <div class="gmail_extra"><br> <div class="gmail_quote"> <div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349m_3449479715428376713m_-614118149965673531h5">On Wed, Aug 30, 2017 at 8:09 PM, Charles Kozler <span dir="ltr">&lt;<a href="mailto:ckozleriii@gmail.com" target="_blank" moz-do-not-send=&quot;true&quot;&gt;ckozleriii(a)gmail.com&lt;/a&gt;&amp;gt;&lt;/span&gt; wrote:<br> </div> </div> <blockquote type="cite"> <div> <div class="m_688166259021271601m_8337997229390174390m_-8986942953698210250m_-6021655538959603885m_5951134109970997349m_3449479715428376713m_-614118149965673531h5"> <div dir="ltr">Hello - <div><br> </div> <div>I have successfully created a hyperconverged hosted engine setup consisting of 3 nodes - 2 for VM's and the third purely for storage. I manually configured it all, did not use ovirt node or anything. Built the gluster volumes myself</div> <div><br> </div> <div>However, I noticed that when setting up the hosted engine and even when adding a new storage domain with glusterfs type, it still asks for hostname:/volumename</div> <div><br> </div> <div>This leads me to believe that if that one node goes down (ex: node1:/data), then ovirt engine wont be able to communicate with that volume because its trying to reach it on node 1 and thus, go down</div> <div><br> </div> <div>I know glusterfs fuse client can connect to all nodes to provide failover/ha but how does the engine handle this?</div> </div> <br> </div> </div> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send=&quot;true&quot;&gt;Users(a)ovirt.org&lt;/a&gt;&lt;br&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr... <br> </blockquote> </div> <br> </div> <br> </blockquote> </div> <br> </div> </div> </div> <br> </blockquote> </div> <br> </div> </div> </div> <br> </blockquote> </div> <br> </div> </div> </div> <br> </blockquote> </div> <br> </div> </div> </div> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send=&quot;true&quot;&gt;Users(a)ovirt.org&lt;/a&gt;&lt;br&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr... <br> </blockquote> </div> <br> </div> <pre>______________________________<wbr>_________________ Users mailing list <a href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send=&quot;true&quot;&gt;Users(a)ovirt.org&lt;/a&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr... </pre> </blockquote> </div> </div> </div> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" target="_blank" moz-do-not-send=&quot;true&quot;&gt;Users(a)ovirt.org&lt;/a&gt;&lt;br&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/mailman<wbr... <br> </blockquote> </div> <br> </div> </div> </div> </blockquote> </div> <br> </div> </div> </div> <br> ______________________________<wbr>_________________<br> Users mailing list<br> <a href="mailto:Users@ovirt.org" moz-do-not-send=&quot;true&quot;&gt;Users(a)ovirt.org&lt;/a&gt;&lt;br&gt; <a href="http://lists.ovirt.org/mailman/listinfo/users" rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.ovirt.org/<wbr>mai... <br> </blockquote> </div> <br> </div> <br> <fieldset class="mimeAttachmentHeader"></fieldset> <br> <pre wrap="">_______________________________________________ Users mailing list <a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://... </pre> </blockquote> <br> </body> </html> --------------9AE8F9DB18CD3709026D88C7--

So also on my engine storage domain. Shouldnt we see the mount options in mount -l output? It appears fault tolerance worked (sort of - see more below) during my test [root@appovirtp01 ~]# grep -i mnt_options /etc/ovirt-hosted-engine/hosted-engine.conf mnt_options=backup-volfile-servers=n2:n3 [root@appovirtp02 ~]# grep -i mnt_options /etc/ovirt-hosted-engine/hosted-engine.conf mnt_options=backup-volfile-servers=n2:n3 [root@appovirtp03 ~]# grep -i mnt_options /etc/ovirt-hosted-engine/hosted-engine.conf mnt_options=backup-volfile-servers=n2:n3 Meanwhile not visible in mount -l output: [root@appovirtp01 ~]# mount -l | grep -i n1:/engine n1:/engine on /rhev/data-center/mnt/glusterSD/n1:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) [root@appovirtp02 ~]# mount -l | grep -i n1:/engine n1:/engine on /rhev/data-center/mnt/glusterSD/n1:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) [root@appovirtp03 ~]# mount -l | grep -i n1:/engine n1:/engine on /rhev/data-center/mnt/glusterSD/n1:_engine type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) So since everything is "pointed" at node 1 for engine storage, I decided to hard shut down node 1 while hosted engine VM runs on node 3 The result was that after ~30 seconds the engine crashed likely because of the gluster 42 second timeout. The hosted engine VM came back up (with node 1 still down) after about 5-7 minutes Is this expected for the VM to go down? I thought gluster fuse mounted all bricks in the volume http://lists.gluster.org/pipermail/gluster-users/2015-May/021989.html so I would imagine this to be more seamless? On Tue, Sep 12, 2017 at 7:04 PM, Charles Kozler <ckozleriii(a)gmail.com&gt; wrote: