Gluster users - Jul 2016 - Rolling Upgrades

On 07/21/2016 03:51 PM, David Gossage wrote:
> In the case of rolling upgrades across a cluster if I have my storage 
> and vm hosts on separate machines what order would I want to update?
>
> Clients first or storage nodes first?

Storage servers first followed by clients is the recommended way.
> */David Gossage/*/*
> */
> //*Carousel Checks Inc.| System Administrator*
> *Office*708.613.2284
>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160721/a54a8006/attachment.html>

On Thu, Jul 21, 2016 at 5:49 AM, Ravishankar N <ravishankar at redhat.com>
wrote:
> On 07/21/2016 03:51 PM, David Gossage wrote:
>
> In the case of rolling upgrades across a cluster if I have my storage and
> vm hosts on separate machines what order would I want to update?
>
> Clients first or storage nodes first?
>
>
>
> Storage servers first followed by clients is the recommended way.
>
Thanks.  And I imagine I would want to leave op-version update till after
clients are updated also.
Clients shouldn't need to refresh mount post op version update should
they?  Just after gluster update to make sure its using updated 3.7.13
files in its mount.

> *David Gossage*
> *Carousel Checks Inc. | System Administrator*
> *Office* 708.613.2284
>
>
> _______________________________________________
> Gluster-users mailing listGluster-users at
gluster.orghttp://www.gluster.org/mailman/listinfo/gluster-users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.gluster.org/pipermail/gluster-users/attachments/20160721/4ed73a24/attachment.html>