Going from 3.6 to 3.7 is very likely not going to happen without down time. I am speaking from experience. Regardless of all the recommendations given about the changes for rpc-auth-allowi-insecure that came in the 3.7.2 to 3.7.3 versions, I was never able to get things upgraded to >= 3.7.3 without downtime. Since you are coming from 3.6.2 to something post 3.7.3, I doubt you will be able to make the upgrade without scheduling downtime as well. Some useful posts: https://www.gluster.org/pipermail/gluster-users/2015-August/023207.html Make sure to read the whole thread of e-mails. https://www.gluster.org/pipermail/gluster-users/2015-September/023470.html HTH, Diego On Tue, May 10, 2016 at 6:27 PM, Lindsay Mathieson <lindsay.mathieson@xxxxxxxxx> wrote: > On 11/05/2016 4:40 AM, Jamie Lawrence wrote: > > - Is anyone currently running Gluster on Debian or Ubuntu in production? We > would prefer to get off RHEL-flavored hosts (currently Centos 7), thus I’m > hoping I’m wrong, but I’ve seen little evidence that trying this for > production would be a safe endeavor.[1] > > > I'm running gluster 3.7.11 on our proxmox cluster, hosting VM's. Based on > debian Jessie, no issues. gluster.org always has uptodate debian packages. > > -- > Lindsay Mathieson > > > _______________________________________________ > 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
