Re: [Gluster-users] Unable to add brick from new fresh installed server into upgraded cluster

2014-11-26 Thread JF Le Fillâtre

Hello Alastair,

The tip to change the operating version number was given in another mail to the 
list within the last few hours:

gluster volume set all cluster.op-version 30600

My own /var/lib/glusterd/glusterd.info files, from a freshly installed 3.6.1, 
contain the following line:

operating-version=30600

But interestingly, the log files on my clients contain lines like:
0-vol2-client-0: Using Program GlusterFS 3.3, Num (1298437), Version (330)

Note that I have no idea if changing the op-version will create side-effects 
that will put your data at risk. Can anyone from Gluster/RedHat provide some 
insight on this topic?

Thanks,
JF


On 25/11/14 20:48, Alastair Neil wrote:
 I have a 2 server CentOS 6 replicated cluster which started out as
 version 3.3 and has been progressively updated  and is now on version
 3.6.1.  Yesterday I added a new freshly installed CentOS 6.6 host and
 wanted to convert to replica 3 on one of my volumes, however I was
 unable to add the brick as it reported that all the brick hosts had to
 be at version 03060.   Presumable some minimum compatibility is set on
 the volume, but I am struggling to find where.  The info file under
 /va/lib/glusterd/vols/volname has op-version=2, client-op-version=2.
 
 Any suggestions?
 
 
 Thanks, Alastair
 
 
 
 
 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-users
 
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users


Re: [Gluster-users] Unable to add brick from new fresh installed server into upgraded cluster

2014-11-26 Thread JF Le Fillâtre

Ah great, thank you Kaushal for the explanation! Duly noted. :)


On 26/11/14 10:53, Kaushal M wrote:
 JF is correct. You'll need to bump up the operating version
 (op-version) to the latest. There have been changes to add-brick and
 the following heal, rebalance etc. which require that all servers be
 at an operating-version greater than or equal to the operating-version
 level introduced in v3.6, 30600.
 The upgrade process will not bump up the operating version of the
 cluster automatically, because we do not want to break clusters in
 between upgrades of two nodes. Once you have upgraded all the nodes in
 the cluster, you can use 'gluster volume set all cluster.op-version
 30600' to bump it up. This could have been done automatically, but we
 don't as automatically doing it could cause older clients to break
 because of newer features being enabled.
 
 ~kaushal
 
 On Wed, Nov 26, 2014 at 3:00 PM, JF Le Fillâtre
 jean-francois.lefilla...@uni.lu wrote:

 Hello Alastair,

 The tip to change the operating version number was given in another mail to 
 the list within the last few hours:

 gluster volume set all cluster.op-version 30600

 My own /var/lib/glusterd/glusterd.info files, from a freshly installed 
 3.6.1, contain the following line:

 operating-version=30600

 But interestingly, the log files on my clients contain lines like:
 0-vol2-client-0: Using Program GlusterFS 3.3, Num (1298437), Version (330)

 Note that I have no idea if changing the op-version will create side-effects 
 that will put your data at risk. Can anyone from Gluster/RedHat provide some 
 insight on this topic?

 Thanks,
 JF


 On 25/11/14 20:48, Alastair Neil wrote:
 I have a 2 server CentOS 6 replicated cluster which started out as
 version 3.3 and has been progressively updated  and is now on version
 3.6.1.  Yesterday I added a new freshly installed CentOS 6.6 host and
 wanted to convert to replica 3 on one of my volumes, however I was
 unable to add the brick as it reported that all the brick hosts had to
 be at version 03060.   Presumable some minimum compatibility is set on
 the volume, but I am struggling to find where.  The info file under
 /va/lib/glusterd/vols/volname has op-version=2, client-op-version=2.

 Any suggestions?


 Thanks, Alastair




 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-users

 ___
 Gluster-users mailing list
 Gluster-users@gluster.org
 http://supercolony.gluster.org/mailman/listinfo/gluster-users

-- 

 Jean-François Le Fillâtre
 ---
 Scientific Collaborator
 LSCB - University of Luxembourg
 ---
 PGP KeyID 0x134657C6
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users

[Gluster-users] Unable to add brick from new fresh installed server into upgraded cluster

2014-11-25 Thread Alastair Neil
I have a 2 server CentOS 6 replicated cluster which started out as version
3.3 and has been progressively updated  and is now on version 3.6.1.
Yesterday I added a new freshly installed CentOS 6.6 host and wanted to
convert to replica 3 on one of my volumes, however I was unable to add the
brick as it reported that all the brick hosts had to be at version 03060.
Presumable some minimum compatibility is set on the volume, but I am
struggling to find where.  The info file under
/va/lib/glusterd/vols/volname has op-version=2, client-op-version=2.

Any suggestions?


Thanks, Alastair
___
Gluster-users mailing list
Gluster-users@gluster.org
http://supercolony.gluster.org/mailman/listinfo/gluster-users