回复: upgrade gluster from old version

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

 



I have upgraded successfully from glusterfs-server 3.7 to 7.7 directly offline . Glusterfs-server 7.7  can't work on centos 7.0 ,after update the os to centos 7.8 ,glusterfs-servers work as expected !  After upgrade ,I added a arbiter node.

Volume Name: datacenter
Type: Replicate
Volume ID: 03fbf2e3-86f0-4d24-a60c-e01560b75e36
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: gluster1:/glusterfs/brick1/datacenter
Brick2: gluster2:/glusterfs/brick1/datacenter
Brick3: arbiter:/home/brick/datacenter (arbiter)
Options Reconfigured:
cluster.self-heal-daemon: enable
transport.address-family: inet
nfs.disable: on
server.allow-insecure: on
performance.readdir-ahead: on
 
Volume Name: vmhome
Type: Replicate
Volume ID: ed391b29-fb88-4524-a589-fc4b10212e2b
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: gluster1:/glusterfs/brick1/vmimage
Brick2: gluster2:/glusterfs/brick1/vmimage
Brick3: arbiter:/home/brick/vmhome (arbiter)
Options Reconfigured:
transport.address-family: inet
nfs.disable: on
performance.readdir-ahead: on
server.allow-insecure: on
storage.owner-uid: 107
storage.owner-gid: 107
[root@gluster2 ~]# 

[root@gluster2 ~]# gluster volume get all cluster.op-version
Option                                  Value                                  
------                                  -----                                  
cluster.op-version                      70200                                  
[root@gluster2 ~]#




发件人: Sanju Rakonde <srakonde@xxxxxxxxxx>
发送时间: 2020年8月26日 3:04
收件人: liu zhijing <jordielau@xxxxxxxxxxx>
抄送: gluster-users@xxxxxxxxxxx List <gluster-users@xxxxxxxxxxx>
主题: Re: upgrade gluster from old version
 
Hi,

I believe you can do an offline upgrade (I have never tried upgrading from 3.7 to 7.7, so there might be issues). 

If you want to do a fresh install, after installing the 7.7 packages, you can use the same old bricks to create the volumes. but you need to add force at the end of volume create command.

On Wed, Aug 26, 2020 at 5:27 AM liu zhijing <jordielau@xxxxxxxxxxx> wrote:
hi everyone!
I found It is hard to upgrade  from a gluster version from 3.7.6 to 7.7,so I remove all the install package and delete all config file except the brick, and I resinstall the glusterfs 7.7, then reconfig the same volume name but use a temp brick.after everything is ok ,then i stop the volume and replace the old brick , change the brick volume id as the new volume id , at last  start the volume successfully.
What I want to know is  if this is the right way to upgrade .


________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users


--
Thanks,
Sanju
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://bluejeans.com/441850968

Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[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