Cool, thanks, that's handy info. What's the situation with mixing versions between client and server? For example I've just noticed that we're using glusterfs 3.4.0.59rhs on some clients (came with CentOS7) to talk to servers running 3.6.2. Is that considered OK, or would it be better to upgrade the clients to the one from the gluster repo? Cheers, Kingsley. On Tue, 2015-02-10 at 15:55 +0530, Kaushal M wrote: > Sticking with the same version would be the best option. But you could > use any 3.6.x release. We do not implement any breaking changes > between minor versions. > > > ~kaushal > > On Tue, Feb 10, 2015 at 3:28 PM, Kingsley > <gluster@xxxxxxxxxxxxxxxxxxx> wrote: > Thinking ahead ... will old versions always be available on > the repo? > > I have a 3.6.2 cluster with 4 servers, one brick per server. > If at some > point in the future one brick should fail and I need to build > a new > brick from scratch, would I have to put 3.6.2 back on, or > would it be OK > to put on the latest 3.6.x, or even the latest 3.x? > > Sticking to the same version feels the safest as long as I can > still get > the software. > > Cheers, > Kingsley. > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users > > > _______________________________________________ > Gluster-users mailing list > Gluster-users@xxxxxxxxxxx > http://www.gluster.org/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
