Gluster users - Mar 2019 - upgrade best practices

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.

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. 
-- 
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/

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190329/d8876f82/attachment.html>

On Fri, Mar 29, 2019, 10:03 PM Jim Kinney <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.
>
> 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
> https://lists.gluster.org/mailman/listinfo/gluster-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.gluster.org/pipermail/gluster-users/attachments/20190329/bafc2cc7/attachment.html>