<div dir="ltr">Sorry, I meant RedHat's Gluster Storage Server 3.2 which is latest and greatest.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 2, 2017 at 9:28 AM, Kaushal M <span dir="ltr"><<a href="mailto:kshlmster@gmail.com" target="_blank">kshlmster@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <<a href="mailto:markconnor64@gmail.com">markconnor64@gmail.com</a>> wrote:<br>
> Can the glusterd daemon be restarted on all storage nodes without causing<br>
> any disruption to data being served or the cluster in general? I am running<br>
> gluster 3.2 using distributed replica 2 volumes with fuse clients.<br>
<br>
</span>Yes, in general. Any clients already connected will still continue to work.<br>
<br>
What can be a problem is new clients, because glusterd may sometimes<br>
not pick up already running bricks. But most of these issues have been<br>
fixed in recent versions of GlusterFS.<br>
So, since you're using GlusterFS-3.2, which is really-really-really<br>
old, you may face this issue.<br>
<br>
You should try to run a more recent and supported version of GlusterFS<br>
if possible. 3.2 is not supported and hasn't been updated in over 5<br>
years.<br>
<br>
> Regards,<br>
> Mark<br>
><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" target="_blank" rel="noreferrer">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</blockquote></div><br></div>