Re: [Gluster-users] standby-server
What ist he reason about a spare server ? With gluster just replicate to the real status all the time!? Or just do geo replication to a non gluster machine!? --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- -Ursprüngliche Nachricht- Von: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] Im Auftrag von Ted Miller Gesendet: Freitag, 16. August 2013 18:29 An: gluster-users@gluster.org Betreff: [Gluster-users] standby-server I am looking at glusterfs for a HA application w/o local tech support (don't ask, third-world country, techs are hard to find). My current plan is to do a replica-4 + hot spare server. Of the four in-use bricks, two will be on servers and the other two will be on a client machine and a hot-backup client machine. No striping, all content on each local machine, each machine using its own disk for all reading. Part of my plan is to have a cold-spare server in the rack, not powered on. (This server will also be a cold spare for another server). I am wondering if this would be a viable way to set up this configuration: Set up glusterfs as replica-5. 1. server1 2. server2 3. client 4. client-standby 5. server-spare Initialize and set up glusterfs with all 5 bricks in the system (no file content). Install system at client site, and test with all 5 bricks in system. Shut down spare server. Once a month, power up spare server, run full heal, shut down. Power up server-spare for any software updates. If server1 or server2 dies (or needs maintenance), tell them to power up server-spare, and let it heal. It seems to me that this would be easier than setting up a replica-4 system and then jumping through all the hoops to replace a server from scratch. Comments, reactions, pot-shots welcome. Ted Miller -- He is no fool who gives what he cannot keep, to gain what he cannot lose. - - Jim Elliot For more information about Jim Elliot and his unusual life, see http://www.christianliteratureandliving.com/march2003/carolyn.html. Ted Miller Design Engineer HCJB Global Technology Center 2830 South 17th St Elkhart, IN 46517 574--970-4272 my desk 574--970-4252 receptionist ___ 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] Slow on writing
I do not think that isssue with network I have just tested mount -t nfs gluster:/volume /mnt and read speed very high on small files: for example: Write 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 0.0357166 s, 573 kB/s read 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 3.15e-05 s, 650 MB/s Write 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 0.0455507 s, 450 kB/s read 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 3.143e-05 s, 652 MB/s Write 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 0.0196823 s, 1.0 MB/s read 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 2.5493e-05 s, 803 MB/s writespeedvery slow under nfs mount ( nfs mount -o rw,rsize=65536,wsize=65536,proto=tcp,soft,intr,noatime,noauto,async,nodiratime 192.168.15.165:/storage /storage) so i renounted /mnt with nas.storage:/storage /storage glusterfs defaults,_netdev 0 0 and got Write 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 0.00244953 s, 8.4 MB/s read 10+0 records in 10+0 records out 20480 bytes (20 kB) copied, 0.00195908 s, 10.5 MB/s as u can see: write speed higher then nfs but read is lower then nfs :) --- Старший Системный Администратор Алексей Шалин ОсОО Хостер kg - http://www.hoster.kg ул. Ахунбаева 123 (здание БГТС) h...@hoster.kg ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Best practices link?
For someone who is implementing gluster for the first time, is there a list of best practices for common scenarios? For eg. what are the series of steps to be done if one is noticing that a node is starting to fail or what does one do to add new storage capacity to a volume? While the admin guide lists most possible commands, it does not really go into such best practices. Thanks in advance. -Ram ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] Meetups?
Thanks, Vijay. Those community days/meetups are going ahead as planned. Look for more content and a schedule this week for each. Thanks, JM - Original Message - On 08/17/2013 09:57 PM, Marcus Bointon wrote: Any more info on the meetups mentioned a while ago? I'd be interested in London on Sep 10th, but I need details before I can book flights. Some details available here: http://www.gluster.org/meetups/ HTH, Vijay ___ 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
[Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer
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) From existing nodes trying to do: # gluster peer probe storage8 peer probe: failed: Peer storage8 is already at a higher op-version How can I get the op-version of existing cluster nodes to the same op-version as the new fresh node so that gluster peer probe storage8 works from existing nodes? From existing nodes I see operating-version=1 Old nodes: # /var/lib/glusterd/glusterd.info UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f operating-version=1 Any help would be appreciated? ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] standby-server
-Ursprüngliche Nachricht- Von: gluster-users-boun...@gluster.org [mailto:gluster-users-boun...@gluster.org] Im Auftrag von Ted Miller Gesendet: Freitag, 16. August 2013 18:29 An: gluster-users@gluster.org Betreff: [Gluster-users] standby-server I am looking at glusterfs for a HA application w/o local tech support (don't ask, third-world country, techs are hard to find). My current plan is to do a replica-4 + hot spare server. Of the four in-use bricks, two will be on servers and the other two will be on a client machine and a hot-backup client machine. No striping, all content on each local machine, each machine using its own disk for all reading. Part of my plan is to have a cold-spare server in the rack, not powered on. (This server will also be a cold spare for another server). I am wondering if this would be a viable way to set up this configuration: Set up glusterfs as replica-5. 1. server1 2. server2 3. client 4. client-standby 5. server-spare Initialize and set up glusterfs with all 5 bricks in the system (no file content). Install system at client site, and test with all 5 bricks in system. Shut down spare server. Once a month, power up spare server, run full heal, shut down. Power up server-spare for any software updates. If server1 or server2 dies (or needs maintenance), tell them to power up server-spare, and let it heal. It seems to me that this would be easier than setting up a replica-4 system and then jumping through all the hoops to replace a server from scratch. Comments, reactions, pot-shots welcome. Ted Miller Ted Miller Design Engineer HCJB Global Technology Center Elkhart, IN 46517 On 8/19/2013 2:38 AM, Daniel Müller wrote: What ist he reason about a spare server ? With gluster just replicate to the real status all the time!? This is a hot, tropical location with terrible power, a lot of lightning storms and only part-time air-conditioning. Hardware failures are common. I am doing what I can to protect against the power problems, but it is still an environment that is very hard on equipment. This system will be business-critical--it is a radio station, and their music and other programs will be on the glusterfs, with downtime beyond seconds becoming dead air. If there is a catastrophic event, I want the spare server to have been off, and thus (most likely) not damaged. It can be brought on-line to restore dual server status. Or just do geo replication to a non gluster machine!? I plan on doing geo-replication, but restoring a multi-terabyte file system over a 4Mb link will take days. We would probably have to rsync the file system to portable drives and fly them over. Hope that helps the perspective a bit. Ted Miller --- EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: muel...@tropenklinik.de Internet: www.tropenklinik.de --- ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users Ted Miller Design Engineer HCJB Global Technology Center Elkhart, IN 46517 ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer
Also in old cluster node logs I see this: [2013-08-19 13:54:24.560339] E [glusterd-handshake.c:900:__glusterd_mgmt_hndsk_version_cbk] 0-management: failed to validate the operating version of peer (storage8) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 4:58 PM Subject: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer 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) From existing nodes trying to do: # gluster peer probe storage8 peer probe: failed: Peer storage8 is already at a higher op-version How can I get the op-version of existing cluster nodes to the same op-version as the new fresh node so that gluster peer probe storage8 works from existing nodes? From existing nodes I see operating-version=1 Old nodes: # /var/lib/glusterd/glusterd.info UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f operating-version=1 Any help would be appreciated? ___ 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] Meetups?
On 19 Aug 2013, at 15:36, John Mark Walker johnm...@gluster.org wrote: Those community days/meetups are going ahead as planned. Look for more content and a schedule this week for each. Great, flight booked! Marcus ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer
Someone has actually just done an upgrade on an existing cluster, from glusterfs-3.4.0-3.el6.x86_64 to glusterfs-3.4.0-8.el6.x86_64 that caused the operating version to change on /var/lib/glusterd/glusterd.info operatiog-version=1 to operating-version=2 But that was RHEL based distribution I'm running Ubuntu 13.04 using the packages from deb http://ppa.launchpad.net/semiosis/ubuntu-glusterfs-3.4/ubuntu raring main On my old cluster nodes I have same version of packages installed, but operating-version=1 on /var/lib/glusterd/glusterd.info file Can I manually edit operating-version=2 on /var/lib/glusterd/glusterd.info file restart glusterd on all old servers and then try gluster peer probe storage8 (storage8 is the newest node without /var/lib/glusterd/glusterd.info file) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 5:35 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer Also in old cluster node logs I see this: [2013-08-19 13:54:24.560339] E [glusterd-handshake.c:900:__glusterd_mgmt_hndsk_version_cbk] 0-management: failed to validate the operating version of peer (storage8) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 4:58 PM Subject: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer 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) From existing nodes trying to do: # gluster peer probe storage8 peer probe: failed: Peer storage8 is already at a higher op-version How can I get the op-version of existing cluster nodes to the same op-version as the new fresh node so that gluster peer probe storage8 works from existing nodes? From existing nodes I see operating-version=1 Old nodes: # /var/lib/glusterd/glusterd.info UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f operating-version=1 Any help would be appreciated? ___ 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___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Vote Now! Gluster-related Talks at OpenStack Summit
There are a ton of talks proposed for OpenStack Summit in Hong Kong. Please take a look and remember to vote early and often! - http://www.gluster.org/2013/08/vote-now-gluster-related-talks-at-openstack-summit/ ___ Announce mailing list annou...@gluster.org http://supercolony.gluster.org/mailman/listinfo/announce ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Announcing the 'Announce' List
As you may have already noticed, I added a new list to gluster.org: Announce. For marketing-type things related to the Gluster community, I send everything to annou...@gluster.org Right now, the only people subscribed to announce are myself and gluster-users, although anyone can subscribe. If you're the type of person who wants only the announcements but not requests for support, then you'll want to subscribe to that list: - http://www.gluster.org/mailman/listinfo/announce or send a note to announce-requ...@gluster.org with subscribe in the subject. -JM ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer
- Original Message - I just edited /var/lib/glusterd/glusterd.info and restarted glusterds Just so I understand, you manually added operating-version=2 to the glusterd.info file? There's probably an issue with the DEB packages for Ubuntu. I'm curious if the Debian packages on download.gluster.org have the same issue. -JM operating-version=2 and peer probe works now From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 6:11 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer Someone has actually just done an upgrade on an existing cluster, from glusterfs-3.4.0-3.el6.x86_64 to glusterfs-3.4.0-8.el6.x86_64 that caused the operating version to change on /var/lib/glusterd/glusterd.info operatiog-version=1 to operating-version=2 But that was RHEL based distribution I'm running Ubuntu 13.04 using the packages from deb http://ppa.launchpad.net/semiosis/ubuntu-glusterfs-3.4/ubuntu raring main On my old cluster nodes I have same version of packages installed, but operating-version=1 on /var/lib/glusterd/glusterd.info file Can I manually edit operating-version=2 on /var/lib/glusterd/glusterd.info file restart glusterd on all old servers and then try gluster peer probe storage8 (storage8 is the newest node without /var/lib/glusterd/glusterd.info file) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 5:35 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer Also in old cluster node logs I see this: [2013-08-19 13:54:24.560339] E [glusterd-handshake.c:900:__glusterd_mgmt_hndsk_version_cbk] 0-management: failed to validate the operating version of peer (storage8) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 4:58 PM Subject: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer 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) From existing nodes trying to do: # gluster peer probe storage8 peer probe: failed: Peer storage8 is already at a higher op-version How can I get the op-version of existing cluster nodes to the same op-version as the new fresh node so that gluster peer probe storage8 works from existing nodes? From existing nodes I see operating-version=1 Old nodes: # /var/lib/glusterd/glusterd.info UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f operating-version=1 Any help would be appreciated? ___ 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 ___ 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___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer
Yes, I manually edited the file. I still have one issue: I see in the logs: -datavol-dht: setattr of uid/gid on gfid:7800cc88-1a5a-4cb6-b63d-e4b11ee9f5bbfilename.foo :gfid:---- failed (Invalid argument) do I need to have same uid/guid on each glusterfs server? As it seems setting uid/gid fails? From: John Mark Walker johnm...@gluster.org To: Xset Mode xsetm...@yahoo.com Cc: gluster-users@gluster.org Sent: Monday, August 19, 2013 7:51 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster, I cant do gluster peer probe newfreshpeer I just edited /var/lib/glusterd/glusterd.info and restarted glusterds Just so I understand, you manually added operating-version=2 to the glusterd.info file? There's probably an issue with the DEB packages for Ubuntu. I'm curious if the Debian packages on download.gluster.org have the same issue. -JM operating-version=2 and peer probe works now From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 6:11 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster,I cant do gluster peer probe newfreshpeer Someone has actually just done an upgrade on an existing cluster, from glusterfs-3.4.0-3.el6.x86_64 to glusterfs-3.4.0-8.el6.x86_64 that caused the operating version to change on /var/lib/glusterd/glusterd.info operatiog-version=1 to operating-version=2 But that was RHEL based distribution I'm running Ubuntu 13.04 using the packages from deb http://ppa.launchpad.net/semiosis/ubuntu-glusterfs-3.4/ubuntu raring main On my old cluster nodes I have same version of packages installed, but operating-version=1 on /var/lib/glusterd/glusterd.info file Can I manually edit operating-version=2 on /var/lib/glusterd/glusterd.info file restart glusterd on all old servers and then try gluster peer probe storage8 (storage8 is the newest node without /var/lib/glusterd/glusterd.info file) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 5:35 PM Subject: Re: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster,I cant do gluster peer probe newfreshpeer Also in old cluster node logs I see this: [2013-08-19 13:54:24.560339] E [glusterd-handshake.c:900:__glusterd_mgmt_hndsk_version_cbk] 0-management: failed to validate the operating version of peer (storage8) From: Xset Mode xsetm...@yahoo.com To: gluster-users@gluster.org gluster-users@gluster.org Sent: Monday, August 19, 2013 4:58 PM Subject: [Gluster-users] After Upgrade of 3.2.7 = 3.4 gluster,I cant do gluster peer probe newfreshpeer 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) From existing nodes trying to do: # gluster peer probe storage8 peer probe: failed: Peer storage8 is already at a higher op-version How can I get the op-version of existing cluster nodes to the same op-version as the new fresh node so that gluster peer probe storage8 works from existing nodes? From existing nodes I see operating-version=1 Old nodes: # /var/lib/glusterd/glusterd.info UUID=ed2b70f4-b0b1-4929-a55a-2f49f4f9580f operating-version=1 Any help would be appreciated? ___ Gluster-users mailing list
[Gluster-users] Call for Participation: Gluster Community Days
If you saw this blog post - http://www.gluster.org/2013/08/gluster-world-tour-coming-to-a-city-near-you/ - then you know we are planning several upcoming Gluster Community Days: August 27 – San Francisco – Rackspace has generously agreed to host this Community Day - http://www.meetup.com/GlusterFS-Silicon-Valley/events/124722542/ September 4 – Stockholm, Sweden – Our first event in the nordic region! - http://red.ht/11JazeE September 10 – London, England – Continuing the Northern road show - http://www.meetup.com/Gluster/London-GB/986272/ September 19 – New Orleans, Louisiana – Co-located with LinuxCon/CloudOpen North America - http://events.linuxfoundation.org/events/linuxcon-north-america/ October 24 – Edinburgh, Scotland – Co-located with LinuxCon/CloudOpen Europe - http://events.linuxfoundation.org/events/linuxcon-europe ...with more on the way later this year and next year. This email is to invite you to participate, either by attending or perhaps speaking. Most of the agendas for these community days have been filled, but there are still some speaking slots available. If you wish us to consider your inclusion in the community day agendas, please send a brief note to cfp (at) gluster.org, enclosing a title for your proposed talk, brief description of its contents, and a brief bio that includes your past speaking appearances. Look forward to seeing you there! -John Mark ___ Announce mailing list annou...@gluster.org http://supercolony.gluster.org/mailman/listinfo/announce ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
[Gluster-users] Call for User Stories Feature Feedback
Greetings, Gluster Users: We're starting up a new Case Studies section on the Gluster project web site, and we need your help populating it with tales of your triumphs and travails. Share with us a bit about how you're using Gluster today, and about what's most important to you as Gluster development moves forward, and you'll help bring Gluster to the attention of new users while bringing your needs and use cases to the attention of the project developers. Tell us about your deployment: * How many Gluster nodes are you running, and what's the hardware and OS you're using to host them? * How much data are you hosting on Gluster? * What Gluster version are you using, and what sort of Gluster volumes (replicated, distributed, etc.) are you using? * What protocol(s) do you use to access your Gluster storage? * Looking ahead to the Gluster roadmap, what features/enhancements would you like to see? * Which features on the Gluster 3.5 Proposed Feature List are you most interested in? (http://www.gluster.org/community/documentation/index.php/Planning35) * Are there any pet bugs or backport requests you're particularly keen to see resolved? (http://www.gluster.org/community/documentation/index.php/Backport_Wishlist) * Anything else you'd like to add, or would like to hear about from other Gluster community members? Please feel free to reply on-list (so we can all learn from your deployment) or off-list (if you'd like your feedback to be more discrete). If we intend to turn your feedback into a case study for the site, we'll follow up with you for any further details or clarification. Thank you! Jason --- Jason Brooks Red Hat Open Source and Standards @jasonbrooks | @redhatopen http://community.redhat.com ___ Gluster-users mailing list Gluster-users@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-users
