The client would be the lesser version in this case. Server @ 3.6.3,
Client @ 3.6.0
The only way to get them to match is to use redhat gluster storage where
you have RHEV hypervisors... which is a bit annoying.
Scott H.
On 7/1/15 10:16 AM, Atin Mukherjee wrote:>
> -Atin
> Sent from one plus one
> On Jul 1, 2015 10:13 PM, "Scott Harvanek" <scott.harvanek at
login.com
> <mailto:scott.harvanek at login.com>> wrote:
> >
> > Scenario-
> >
> > Gluster bricks running Gluster 3.6.3, RHEL clients running RH
> provided gluster 3.6.0.53 ( no way to change this, operating version
> 30600 I presume ).
> We do not encourage to use mix and match of upstream and downstream
> versions. IIRC, op-version of 3.6.0.53 must be 30004 (please confirm)
> which means client is higher version than server which is again not a
> recommended setup.
> >
> > If we create a new cluster can the op-version be set down to 30600
> on the 3.6.3 bricks? - Currently - operating-version=30603 by default.
> >
> > --
> > Scott H.
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org <mailto: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/20150701/d370299e/attachment.html>