mabi
2018-Aug-21 13:33 UTC
[Gluster-users] Possibly missing two steps in upgrade to 4.1 guide
Hello, I just upgraded from 4.0.2 to 4.1.2 using the official documentation: https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/ I noticed that this documentation might be missing the following two additional steps: 1) restart the glustereventsd service 2) umount and mount again gluster fuse mounts on clients after upgrading the clients (if using glusterfs fuse mounts of course) Best regards, M.
Hu Bert
2018-Aug-21 14:11 UTC
[Gluster-users] Possibly missing two steps in upgrade to 4.1 guide
I think point 2 is already covered by the guide; see: "Upgrade procedure for clients" Following are the steps to upgrade clients to the 4.1.x version, NOTE: x is the minor release number for the release>>> Unmount all glusterfs mount points on the clientStop all applications that access the volumes via gfapi (qemu, etc.) Install Gluster 4.1>>> Mount all gluster sharesStart any applications that were stopped previously in step (2) 2018-08-21 15:33 GMT+02:00 mabi <mabi at protonmail.ch>:> Hello, > > I just upgraded from 4.0.2 to 4.1.2 using the official documentation: > > https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/ > > I noticed that this documentation might be missing the following two additional steps: > > 1) restart the glustereventsd service > 2) umount and mount again gluster fuse mounts on clients after upgrading the clients (if using glusterfs fuse mounts of course) > > Best regards, > M. > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > https://lists.gluster.org/mailman/listinfo/gluster-users
Shyam Ranganathan
2018-Aug-21 15:11 UTC
[Gluster-users] Possibly missing two steps in upgrade to 4.1 guide
On 08/21/2018 09:33 AM, mabi wrote:> Hello, > > I just upgraded from 4.0.2 to 4.1.2 using the official documentation: > > https://docs.gluster.org/en/latest/Upgrade-Guide/upgrade_to_4.1/ > > I noticed that this documentation might be missing the following two additional steps: > > 1) restart the glustereventsd serviceUpdates to the document submitted here [1], reviews welcome. Thanks for reporting this. Shyam [1] https://github.com/gluster/glusterdocs/pull/410