[Gluster-users] upgrade best practices

[Hari Gowtham]

Hi,

As mentioned above you need not stop the whole cluster and then
upgrade and restart the gluster processes.
We did do the basic rolling upgrade test
with replica volume. And things turned out fine.
There was this minor issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1694010

To overcome this, you will have to check if your upgraded node is
getting disconnect. if it does, then you will have to
1) stop glusterd service on all the nodes (only glusterd)
2) flush the iptables (iptables -F)
3) start glusterd

If you are fine with stopping your service and upgrading all nodes at
the same time,
You can go ahead with that as well.

On Sun, Mar 31, 2019 at 11:02 PM Soumya Koduri <skoduri at redhat.com> wrote:
>
>
>
> On 3/29/19 10:39 PM, Poornima Gurusiddaiah wrote:
> >
> >
> > On Fri, Mar 29, 2019, 10:03 PM Jim Kinney <jim.kinney at gmail.com
> > <mailto:jim.kinney at gmail.com>> wrote:
> >
> >     Currently running 3.12 on Centos 7.6. Doing cleanups on split-brain
> >     and out of sync, need heal files.
> >
> >     We need to migrate the three replica servers to gluster v. 5 or 6.
> >     Also will need to upgrade about 80 clients as well. Given that a
> >     complete removal of gluster will not touch the 200+TB of data on 12
> >     volumes, we are looking at doing that process, Stop all clients,
> >     stop all glusterd services, remove all of it, install new version,
> >     setup new volumes from old bricks, install new clients, mount
> >     everything.
> >
> >     We would like to get some better performance from nfs-ganesha mounts
> >     but that doesn't look like an option (not done any parameter tweaks
> >     in testing yet). At a bare minimum, we would like to minimize the
> >     total downtime of all systems.
>
> Could you please be more specific here? As in are you looking for better
> performance during upgrade process or in general? Compared to 3.12,
> there are lot of perf improvements done in both glusterfs and esp.,
> nfs-ganesha (latest stable - V2.7.x) stack. If you could provide more
> information about your workloads (for eg., large-file,small-files,
> metadata-intensive) , we can make some recommendations wrt to configuration.
>
> Thanks,
> Soumya
>
> >
> >     Does this process make more sense than a version upgrade process to
> >     4.1, then 5, then 6? What "gotcha's" do I need to be ready for? I
> >     have until late May to prep and test on old, slow hardware with a
> >     small amount of files and volumes.
> >
> >
> > You can directly upgrade from 3.12 to 6.x. I would suggest that rather
> > than deleting and creating Gluster volume. +Hari and +Sanju for further
> > guidelines on upgrade, as they recently did upgrade tests. +Soumya to
> > add to the nfs-ganesha aspect.
> >
> > Regards,
> > Poornima
> >
> >     --
> >
> >     James P. Kinney III
> >
> >     Every time you stop a school, you will have to build a jail. What you
> >     gain at one end you lose at the other. It's like feeding a dog on his
> >     own tail. It won't fatten the dog.
> >     - Speech 11/23/1900 Mark Twain
> >
> >     http://heretothereideas.blogspot.com/
> >
> >     _______________________________________________
> >     Gluster-users mailing list
> >     Gluster-users at gluster.org <mailto:Gluster-users at gluster.org>
> >     https://lists.gluster.org/mailman/listinfo/gluster-users
> >



-- 
Regards,
Hari Gowtham.