<div dir="ltr"><div>As long as there are enough nodes to satisfy quorum, the volumes should remain R/W. Have you tried writing to the volume during this period? Anything in your logs?<br><br></div>Doug<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 20 January 2017 at 17:06, Ziemowit Pierzycki <span dir="ltr"><<a href="mailto:ziemowit@pierzycki.com" target="_blank">ziemowit@pierzycki.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I have a 4-node gluster with distributed-replicated volumes that serve<br>
out VM images. The purpose of using gluster was to provide highly<br>
available storage for our virtualization platform. When performing<br>
maintenance on one of the gluster nodes, I noticed the VM storage<br>
becomes unavailable for the duration of the node being shutdown and<br>
while the heal is running. Each VM qemu process connects to gluster<br>
directly and needs to be restarted in order to bring up the VM again.<br>
<br>
So, is the setup wrong or does gluster not provide high availability?<br>
<br>
Thanks,<br>
<br>
Ziemowit<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div>