After Upgrade of 3.2.7 => 3.4 gluster, I cant do gluster peer probe newfreshpeer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I followed following instructions to upgrade existing gluster cluster 3.2.7 to 3.4 gluster on Ubuntu 13.04


http://vbellur.wordpress.com/2012/05/31/upgrading-to-glusterfs-3-3/

I stopped all glusterd and client processes first.

I had to copy files from /etc/glusterd/ to /var/lib/glusterd as the location has changed in 3.4

I also had to do the following to be able to start the volume after upgrade:

vol=datavol; brick=/home/glusterfs; setfattr -n trusted.glusterfs.volume-id -v 0x$(grep volume-id /var/lib/glusterd/vols/$vol/info | cut -d= -f2 | sed 's/-//g') $brick


All old nodes were upgraded to packages from the repository

ii? glusterfs-client??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? clustered file-system (client package)
ii? glusterfs-common??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? GlusterFS common libraries and translator modules
ii? glusterfs-server??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? clustered file-system (server package)



Now when I try to add a new fresh Ubuntu 13.04 node with same packages


ii? glusterfs-client??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? clustered file-system (client package)
ii? glusterfs-common??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? GlusterFS common libraries and translator modules
ii? glusterfs-server??????????????????? 3.4.0final-ubuntu1~raring1?????? amd64??????? clustered file-system (server package)



[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux