Il 26 mag 2016 20:09, "Dj Merrill" <gluster@xxxxxxxx> ha scritto:
> Our upgrade procedure is to upgrade the servers first (shutdown the
> Gluster service on a server, upgrade that server, then reboot, then go
> to the next server once it has come back online and sync'ed), then the
> clients one by one. No downtime, except rebooting the individual
> machines one by one as running tasks allow.
Ad long as clients are able to talk with newer server
let's take MySQL as example.
Mysqldump 5.5 is unable to talk to MySQL 5.6 due to removed support for "SET OPTIONS"
> Gluster services our HPC Grid so it is not uncommon to have a client on
> the previous version for several days until jobs finish running on it so
> it can be rebooted. Note this is going between minor revisions, like
> 3.7.x to 3.7.y.
And what about major version like 3.5 to 3.6 or 3.7?
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
