Sorry, I meant RedHat's Gluster Storage Server 3.2 which is latest and greatest.
On Wed, Aug 2, 2017 at 9:28 AM, Kaushal M <[email protected]> wrote: > On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <[email protected]> > wrote: > > Can the glusterd daemon be restarted on all storage nodes without causing > > any disruption to data being served or the cluster in general? I am > running > > gluster 3.2 using distributed replica 2 volumes with fuse clients. > > Yes, in general. Any clients already connected will still continue to work. > > What can be a problem is new clients, because glusterd may sometimes > not pick up already running bricks. But most of these issues have been > fixed in recent versions of GlusterFS. > So, since you're using GlusterFS-3.2, which is really-really-really > old, you may face this issue. > > You should try to run a more recent and supported version of GlusterFS > if possible. 3.2 is not supported and hasn't been updated in over 5 > years. > > > Regards, > > Mark > > > > _______________________________________________ > > Gluster-users mailing list > > [email protected] > > http://lists.gluster.org/mailman/listinfo/gluster-users >
_______________________________________________ Gluster-users mailing list [email protected] http://lists.gluster.org/mailman/listinfo/gluster-users
