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