Hello all, I have a relatively straightforward 4-node gluster setup (2 clients, 2 servers, client-side replication) running version 2.0.9 across the board. We are considering upgrading to 3.1.0 . The documentation indicates that it would be as simple as: - shut gluster down - uninstall the previous packages (we package install everything) - install the new packages - generate the new server and client configs - start everything up Beyond what is indicated above, is there any particular upgrade path or specific concerns we will need to address ? Thank you. -- Daniel Maher <dma+gluster AT witbe DOT net>
Daniel, I just asked this question earlier this month, see http://gluster.org/pipermail/gluster-users/2010-November/005801.html for that thread. It was also recommended that i wait for 3.1.1 which was released today i believe. thanks, liam On Mon, Nov 29, 2010 at 9:37 AM, Daniel Maher <dma+gluster at witbe.net> wrote:> Hello all, > > I have a relatively straightforward 4-node gluster setup (2 clients, 2 > servers, client-side replication) running version 2.0.9 across the board. > > We are considering upgrading to 3.1.0 . ?The documentation indicates that it > would be as simple as: > - shut gluster down > - uninstall the previous packages (we package install everything) > - install the new packages > - generate the new server and client configs > - start everything up > > Beyond what is indicated above, is there any particular upgrade path or > specific concerns we will need to address ? > > Thank you. > > > -- > Daniel Maher <dma+gluster AT witbe DOT net> > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users >
On Mon, Nov 29, 2010 at 06:37:22PM +0100, Daniel Maher wrote:> I have a relatively straightforward 4-node gluster setup (2 clients, 2 > servers, client-side replication) running version 2.0.9 across the board. > > We are considering upgrading to 3.1.0 . The documentation indicates > [...] > Beyond what is indicated above, is there any particular upgrade path or > specific concerns we will need to address ?The unify translator is no longer supported. You have to change it to DHT, if it matters for you. As I understand, DHT has no load balancing mechanism (may put all big files in a single subvolume) and for me it is the reason for staying with 2.0. Krzysztof