On Mon, 2014-04-14 at 17:29 -0700, Harshavardhana wrote: > > > > Just distributed. > > > > Pure distributed setup you have to take a downtime, since the data > isn't replicated. If I shutdown the server processes, wont the clients just wait for it to come back up? Ie like NFS hard mounts? I don't mind an interruption, I just want to avoid killing all jobs that are currently accessing the filesystem if at all possible, our users have suffered a lot recently with filesystem outages. By the way, how does one shutdown the glusterfs processes without stopping a volume? It would be nice to have a quiesce or freeze option that just stalls all access while maintenance takes place. > > >> > >> > 3.4.1 to 3.4.3-3 shouldn't cause problems with existing clients and > >> > other servers, right? > >> > > >> > >> You mean 3.4.1 and 3.4.3 co-existent with in a cluster? > > > > Yes, at least for the duration of the upgrade. > > Yeah 3.4.x series is backward compatible to each other in any case. > _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
