-Atin
Sent from one plus one
On Jul 1, 2015 10:49 PM, "Scott Harvanek" <scott.harvanek@xxxxxxxxx> wrote:
>
> 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.
Well if you are talking about rhs 3.6.0.53 as a client then definitely the op version is not 30600 and also my question is why would you want to bump down your server's cluster op version?
>
> 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@xxxxxxxxx> 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@xxxxxxxxxxx
>> > http://www.gluster.org/mailman/listinfo/gluster-users
>
>
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://www.gluster.org/mailman/listinfo/gluster-users
