[Gluster-users] upgrading from 2.0.9 to 3.1, any gotchas?

Craig Carl craig at gluster.com
Sat Nov 13 02:44:00 UTC 2010

Liam - 
The upgrade guide is below [1], it's pretty much a rip and replace but it shouldn't take more than a couple of minutes. Your data is not touched, but backups are always a good idea! Some things to watch for - 

1. There are no longer volume files, you configure Gluster using the `gluster` command, Gluster uses RPC to distribute the configuration everywhere. The possible issue there is that you need to "recreate" your current configuration with the new `gluster` tool. The `gluster` command will work without a problem almost all of the time but if you have a very complicated, or non-standard vol file it may not. If you want me to look at it you can send your current vol file to the list or me directly. (we have a workaround if your config isn't compatible.) 

2. Gluster ships with a NFS server implemented as a translator, make sure you don't have another NFS server running on the server. On most disti's rpcbind or portmap and nfs-utils or nfs-common are required. 

3. We have implemented much more aggressive locking in this version to significantly reduce the possibility of split brain. This has resulted in a unacceptable performance impact. The engineering team has been working around the clock to resolve the issue, version 3.1.1 will be out next week and will be faster than 3.1, you may want to wait. 

4. Solaris support for glusterfsd will be available in version 3.2. 

[1] http://www.gluster.com/community/documentation/index.php/Gluster_3.0_to_3.1_Upgrade_Guide 

Please let me know if you have any other questions. 



Craig Carl 
Senior Systems Engineer; Gluster, Inc. 

Cell - ( 408) 829-9953 (California, USA) 
Office - ( 408) 770-1884 
Gtalk - craig.carl at gmail.com 
Twitter - @gluster 
Installing Gluster Storage Platform, the movie! 

From: "Liam Slusser" <lslusser at gmail.com> 
To: gluster-users at gluster.org 
Sent: Friday, November 12, 2010 6:26:11 PM 
Subject: [Gluster-users] upgrading from 2.0.9 to 3.1, any gotchas? 

Hey Gluster Users, 

Been awhile since i've posted here. I'm looking to upgrade our 150tb 
10 brick cluster from 2.0.9 to 3.1. Is there any gotcha's that i 
should be aware of? Anybody run into any problems? Any suggestions 
or hints would be most helpful. I hoping the new Gluster will be a 
bit more forgiving on split brain issues and an increase in 
performance is always welcome. 

Gluster-users mailing list 
Gluster-users at gluster.org 

More information about the Gluster-users mailing list