GaussDB T 分布式集群从1.0.1升级至1.0.2

原创 gelyon 2020-03-11

1480

分布式集群升级

GaussDB T分布式集群通过执行gs_upgradectl命令对数据库版本进行升级，升级有两种方式：离线升级和在线滚动升级。

对于GaussDB T 1.0.1版本仅支持离线升级，离线升级类型也仅支持离线二进制升级和离线小版本升级两种类型。对于1.0.2版本的升级，要求升级源版本和升级所使用的目标版本必须同时满足【升级版本规则】和【升级白名单】时，才可执行升级操作。

本示例仅介绍GaussDB T分布式集群通过gs_upgradectl离线升级方式，从1.0.1版本升级至1.0.2版本，其它版本的升级请参考官方文档说明。

1、关于gs_upgradectl命令说明

$ which gs_upgradectl 
/u01/gaussdb/gaussTools/wisequery/script/gs_upgradectl
$ gs_upgradectl --help

gs_upgradectl is a utility to upgrade a cluster.

Usage:
  gs_upgradectl -? | --help
  gs_upgradectl -V | --version

  gs_upgradectl -t upgrade-type -X XMLFILE [-l LOGFILE]
  gs_upgradectl -t offline-upgrade -X XMLFILE [-l LOGFILE]
  gs_upgradectl -t offline-rollback -X XMLFILE [-l LOGFILE]

General options:
  -?, --help                      Show help information for this utility, and exit the command line mode.
  -V, --version                   Show version information.
  -t                              Subcommand for upgrade. It can be upgrade-type,
                                  offline-upgrade, offline-rollback.
  -X                              Path of the XML configuration file of the later version cluster.
  -l                              Path of log file.

$
复制

说明：
-X ：指定集群的配置文件。
-l ：升级或回滚过程的日志文件绝对路径。
-t ：指定离线升级类型。
取值范围：upgrade-type、auto-upgrade、auto-rollback、binary-upgrade、binary-rollback、systable-upgrade、systable-rollback和commit-upgrade。
其中upgrade-type为判断本次离线升级的类型，systable-upgrade为离线小版本升级，binary-upgrade为离线二进制升级。

2、关于升级白名单

对于1.0.2版本的升级，升级源版本和升级所使用的目标版本必须同时满足【升级版本规则】和【升级白名单】的要求时，才可执行升级操作。具体【升级版本规则】，请查看官方1.0.2产品文档手册7.5.1章节说明。
升级白名单是指具体规定的可升级的版本。升级白名单随版本发布，以文件的形式存放在安装软件包解压的根目录下，文件名称为GaussDB_T-Upgrade-WhiteList.txt，解压安装包后与script同级，不建议修改。如不配置升级白名单，系统检查升级版本规则后，符合规则直接执行升级；不符合规则则报错退出。
升级白名单GaussDB_T-Upgrade-WhiteList.txt文件内容如下：

# cd /software/gaussdb/
# cat GaussDB_100-Upgrade-WhiteList.txt 
########################################################################################
# Please follow the fourth line format!                                                #
# SOURCE-VERSION                TARGET-VERSION                       UPGRADE-MODE      #
# GaussDB_100_1.0.0.B019        GaussDB_100_1.0.1.B019               online|offline    #
########################################################################################

SOURCE-VERSION                  TARGET-VERSION                       UPGRADE-MODE      
# 
复制

参数说明如下：
字段名字段含义取值范围
SOURCE-VERSION 可升级的源版本
TARGET-VERSION 可升级的目标版本
UPGRADE-MODE 可升级的类型 ● online：仅支持滚动升级。● offline：仅支持离线升级。● online|offline：既支持离线升级，也支持滚动升级。

3、离线升级注意事项

GaussDB T 1.0.1版本仅支持离线升级，需要注意以下事项：（升级前，请严格阅读以下相关注意事项，并确认）
 集群内所有节点Python版本要求3.7.2及以上。
 集群用户互信正常。
 升级前需保证集群健康状态正常，所有CN、DN和GTS的状态正常。
 仅支持离线升级，离线升级仅支持离线小版本升级和离线二进制升级。
 仅支持从低版本往高版本升级。
 离线升级前请停止所有业务，且保证升级过程中没有任何业务在执行。
 离线升级前必须确保GTS组和各DN组中主备实例的信息完全同步，且保持升级前长时间稳定同步。
 升级操作不能和主机替换、扩容、节点替换等其他om侧操作同时执行。
 升级期间不能直接使用cm命令对集群进行操作，比如switchover等。
 升级前需要在目标安装包解压出的script目录下执行前置脚本gs_preinstall。
 离线升级过程中如果已经升级到集群拉起操作（离线二进制升级）或DN正常拉起操作时（离线小版本升级），则不可执行回滚操作。
 升级命令中传入的xml配置文件必须与当前运行集群的配置结构完全相同。
 二进制升级后，未执行commit-upgrade进行升级提交的情况下仍可以执行回滚操作，如果验证确认升级成功后，可以执行commit-upgrade命令以删除升级临时文件。
 小版本升级最后，如果CN和DN均处于READ ONLY模式下，则可以执行回滚；如果CN或主DN处于READ WRITE模式，则不可执行回滚。其中，CN、DN的模式可通过查询DV_DATABASE的OPEN_STATUS字段获取。如果验证确认升级成功，可以执行commit-upgrade命令以删除升级临时文件。
 升级命令执行成功后，如果已执行commit-upgrade命令进行升级提交，则无法再通过调用回滚接口auto-rollback或binary-rollback、systable-rollback回退到老版本。

4、升级前集群检查

4.1、集群状态检查

升级前查看整个集群状态是否正常，CN\DN等是否都能连接，如下：

[omm@gsdb11 ~]$ gs_om -t status
Set output to terminal.
--------------------------------------------------------------------Cluster Status------------------------------------------------------------------
--az_state :      single_az
cluster_state : Normal
balanced :      true
----------------------------------------------------------------------AZ Status---------------------------------------------------------------------
--AZ:AZ1                ROLE:primary            STATUS:ONLINE      
---------------------------------------------------------------------Host Status--------------------------------------------------------------------
--HOST:gsdb11           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.126
HOST:gsdb12           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.127
HOST:gsdb13           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.128
HOST:gsdb14           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.129
----------------------------------------------------------------Cluster Manager Status--------------------------------------------------------------
--INSTANCE:CM1          ROLE:slave              STATUS:ONLINE       HOST:gsdb11           ID:601
INSTANCE:CM2          ROLE:slave              STATUS:ONLINE       HOST:gsdb12           ID:602
INSTANCE:CM3          ROLE:primary            STATUS:ONLINE       HOST:gsdb13           ID:603
INSTANCE:CM4          ROLE:slave              STATUS:ONLINE       HOST:gsdb14           ID:604
---------------------------------------------------------------------ETCD Status--------------------------------------------------------------------
--INSTANCE:ETCD1        ROLE:follower           STATUS:ONLINE       HOST:gsdb11           ID:701      PORT:2379         DataDir:/u01/gaussdb/data/etcd
INSTANCE:ETCD2        ROLE:follower           STATUS:ONLINE       HOST:gsdb12           ID:702      PORT:2379         DataDir:/u01/gaussdb/data/etcd
INSTANCE:ETCD3        ROLE:leader             STATUS:ONLINE       HOST:gsdb13           ID:703      PORT:2379         DataDir:/u01/gaussdb/data/etcd
----------------------------------------------------------------------CN Status---------------------------------------------------------------------
--INSTANCE:cn_401       ROLE:no role            STATUS:ONLINE       HOST:gsdb11           ID:401      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_402       ROLE:no role            STATUS:ONLINE       HOST:gsdb12           ID:402      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_403       ROLE:no role            STATUS:ONLINE       HOST:gsdb13           ID:403      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_404       ROLE:no role            STATUS:ONLINE       HOST:gsdb14           ID:404      PORT:8000         DataDir:/u01/gaussdb/data/cn
---------------------------------------------------------Instances Status in Group (group_1)--------------------------------------------------------
--INSTANCE:DB1_1        ROLE:primary            STATUS:ONLINE       HOST:gsdb11           ID:1        PORT:40000        DataDir:/u01/gaussdb/data/dn1
INSTANCE:DB1_2        ROLE:standby            STATUS:ONLINE       HOST:gsdb12           ID:2        PORT:40021        DataDir:/u01/gaussdb/data/dn1
---------------------------------------------------------Instances Status in Group (group_2)--------------------------------------------------------
--INSTANCE:DB2_3        ROLE:primary            STATUS:ONLINE       HOST:gsdb12           ID:3        PORT:40000        DataDir:/u01/gaussdb/data/dn2
INSTANCE:DB2_4        ROLE:standby            STATUS:ONLINE       HOST:gsdb13           ID:4        PORT:40021        DataDir:/u01/gaussdb/data/dn2
---------------------------------------------------------Instances Status in Group (group_3)--------------------------------------------------------
--INSTANCE:DB3_5        ROLE:primary            STATUS:ONLINE       HOST:gsdb13           ID:5        PORT:40000        DataDir:/u01/gaussdb/data/dn3
INSTANCE:DB3_6        ROLE:standby            STATUS:ONLINE       HOST:gsdb14           ID:6        PORT:40021        DataDir:/u01/gaussdb/data/dn3
---------------------------------------------------------Instances Status in Group (group_4)--------------------------------------------------------
--INSTANCE:DB4_8        ROLE:standby            STATUS:ONLINE       HOST:gsdb11           ID:8        PORT:40021        DataDir:/u01/gaussdb/data/dn4
INSTANCE:DB4_7        ROLE:primary            STATUS:ONLINE       HOST:gsdb14           ID:7        PORT:40000        DataDir:/u01/gaussdb/data/dn4
-----------------------------------------------------------------------Manage IP--------------------------------------------------------------------
--HOST:gsdb11           IP:192.168.179.126
HOST:gsdb12           IP:192.168.179.127
HOST:gsdb13           IP:192.168.179.128
HOST:gsdb14           IP:192.168.179.129
-------------------------------------------------------------------Query Action Info----------------------------------------------------------------
--HOSTNAME: gsdb11     TIME: 2020-03-06 21:29:02.970463
------------------------------------------------------------------------Float Ip------------------------------------------------------------------
HOST:gsdb14    DB4_7:192.168.179.129    IP:
HOST:gsdb11    DB1_1:192.168.179.126    IP:
HOST:gsdb13    DB3_5:192.168.179.128    IP:
HOST:gsdb12    DB2_3:192.168.179.127    IP:
[omm@gsdb11 ~]$
复制

4.2 检查数据库版本

升级前查看数据库版本信息，连接CN执行如下：

[omm@gsdb11 ~]$ zsql omm/yhadmin_123@192.168.179.126:8000 -q

connected.

SQL> select * from v$version;

VERSION                                                         
----------------------------------------------------------------
GaussDB_100_1.0.1.B023 Release d92e025                          
ZENGINE                                                         
d92e025                                                         

3 rows fetched.
	
SQL> select name,status,open_status,database_role from v$database;

NAME            STATUS     OPEN_STATUS     DATABASE_ROLE            
--------------- ---------- --------------- -------------------------
YHDB            OPEN       READ WRITE      PRIMARY                  

1 rows fetched.

SQL> exit

[omm@gsdb11 ~]$
复制

4.3、检查DN主备数据同步情况

升级前检查集群各DN节点主备数据是否同步，如下：
gsdb11主机DN1：

[omm@gsdb11 ~]$ zsql / as sysdba 192.168.179.126:40000 -D /u01/gaussdb/data/dn1 -q

connected.

SQL> select local_lfn, peer_lfn from dv_ha_sync_info;

LOCAL_LFN            PEER_LFN            
-------------------- --------------------
62226                62226               

1 rows fetched.

SQL> exit

[omm@gsdb11 ~]$
复制

gsdb12主机DN2：

[omm@gsdb12 ~]$  zsql / as sysdba 192.168.179.127:40000 -D /u01/gaussdb/data/dn2 -q

connected.

SQL> select local_lfn, peer_lfn from dv_ha_sync_info;

LOCAL_LFN            PEER_LFN            
-------------------- --------------------
62195                62195               

1 rows fetched.

SQL> exit

[omm@gsdb12 ~]$
复制

gsdb13主机DN3：

[omm@gsdb13 ~]$ zsql / as sysdba 192.168.179.128:40000 -D /u01/gaussdb/data/dn3 -q

connected.

SQL> select local_lfn, peer_lfn from dv_ha_sync_info;
	
LOCAL_LFN            PEER_LFN            
-------------------- --------------------
62160                62160               

1 rows fetched.

SQL> exit

[omm@gsdb13 ~]$
复制

gsdb14主机DN4：

[omm@gsdb14 ~]$ zsql / as sysdba 192.168.179.129:40000 -D /u01/gaussdb/data/dn4 -q

connected.

SQL> select local_lfn, peer_lfn from dv_ha_sync_info;

LOCAL_LFN            PEER_LFN            
-------------------- --------------------
62189                62189               

1 rows fetched.

SQL> exit

[omm@gsdb14 ~]$
复制

5、上传目标版本安装包

在任意一个主机节点下，使用omm用户上传目标版本安装包并解压，omm用户需要对目标版本安装包所在目录有读、写和执行权限。

[omm@gsdb11 ~]$ mkdir -p /u01/gaussdb/upgrade
[omm@gsdb11 ~]$ cd /u01/gaussdb/upgrade/
[omm@gsdb11 upgrade]$ ls -l
total 165460
-rw-r----- 1 omm dbgrp 169431040 3月   6 22:02 GaussDB_T_1.0.2-ZBQL7.6-ARM.tar.gz
[omm@gsdb11 upgrade]$
[omm@gsdb11 upgrade]$ tar -xvf GaussDB_T_1.0.2-ZBQL7.6-ARM.tar.gz 
......
......
[omm@gsdb11 upgrade]$ ls -l
total 277096
-rw-r----- 1 omm dbgrp 169431040 3月   6 22:02 GaussDB_T_1.0.2-ZBQL7.6-ARM.tar.gz
-rw-r----- 1 omm dbgrp    19264 3月   9 17:41 DIALECT-SCRIPT-GaussDB_T_1.0.2.tar.gz
-rw-r----- 1 omm dbgrp  1886584 3月   9 17:41 GaussDB_T_1.0.2-CLIENT-C-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp  3788329 3月   9 17:41 GaussDB_T_1.0.2-CLIENT-GO.tar.gz
-rw-r----- 1 omm dbgrp   411955 3月   9 17:41 GaussDB_T_1.0.2-CLIENT-JDBC.tar.gz
-rw-r----- 1 omm dbgrp  1818761 3月   9 17:41 GaussDB_T_1.0.2-CLIENT-ODBC-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp  2053856 3月   9 17:41 GaussDB_T_1.0.2-CLIENT-PYTHON3-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp 64588500 3月   9 17:41 GaussDB_T_1.0.2-CLUSTER-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp 41178751 3月   9 17:41 GaussDB_T_1.0.2-CM-KYLINREDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp  8395154 3月   9 17:41 GaussDB_T_1.0.2-DATABASE-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp   135264 3月   9 17:41 GaussDB_T_1.0.2-ROACH-KYLINREDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp 48123385 3月   9 17:41 GaussDB_T_1.0.2-TOOLS.tar.gz
-rw-r----- 1 omm dbgrp  4281803 3月   9 17:41 GaussDB_T_1.0.2-ZSQL-REDHAT-64bit.tar.gz
-rw-r----- 1 omm dbgrp      533 3月   9 17:41 GaussDB_T-Upgrade-WhiteList.txt
drwxr-x--- 9 omm dbgrp      227 3月   9 17:41 lib
drwxr-x--- 6 omm dbgrp     4096 3月   9 17:41 script
drwxr-x--- 6 omm dbgrp       60 3月   9 17:41 shardingscript
drwxr-x--- 2 omm dbgrp      119 3月   9 17:41 template
[omm@gsdb11 upgrade]$
[omm@gsdb11 upgrade]$ cd script/
[omm@gsdb11 script]$ ls
config       gs_backup  gs_checkclusterinfo  gs_checkperf  gs_expand     gs_install  gs_om             gs_preinstall  gs_register  gs_shrink    gs_testclustercuid  gs_upgradectl  impl         local
gs_allinone  gs_check   gs_checkos           gs_collector  gs_gucZenith  gs_mount    gs_postuninstall  gspylib        gs_replace   gs_sshexkey  gs_uninstall        gs_wsr         __init__.py
[root@gsdb11 script]#
复制

6、升级预检查

在root用户下，进入目标安装包解压出的script目录，执行该目录下的gs_preinstall命令进行升级前置检查，如下：

[root@gsdb11 ~]$ cd /u01/gaussdb/upgrade/script/
[root@gsdb11 script]$ ./gs_preinstall -U omm -G dbgrp  -X /software/gaussdb/clusterconfig.xml  --alarm-type=1 --operation=upgrade
Parsing the configuration file.
Successfully parsed the configuration file.
Do preinstall for upgrade.
Check environment for upgrade preinstall.
Successfully check environment for upgrade preinstall.
Installing the tools on the local node.
Successfully installed the tools on the local node.
Creating SSH trust for the root permission user.
Please enter password for root.
Password:     --输入root用户密码
Successfully created SSH trust for the root permission user.
Distributing package.
Successfully distributed package.
Check old environment on all nodes.
Successfully check old environment on all nodes.
Installing the tools in the cluster.
Successfully installed the tools in the cluster.
Creating conninfo directory.
Successfully created conninfo directory.
Fixing server package owner.
Successfully fixed server package owner.
Add sudo permission for omm.
Successfully add sudo permission for omm
Clean SSH trust for the root permission user.
Successfully cleaned SSH trust for the root permission user.
Preinstallation succeeded.
[root@gsdb11 script]$
复制

如果执行预升级检查gs_preinstall时报错，/usr/bin/env : python3: No such file or directory，原因是缺少python3执行命令，请检查系统python版本和环境。
GaussDB T 1.0.2要求python版本为3.7.2及以上，如果系统没有python3环境，请先安装配置python3环境再操作。
具体python3.x环境配置，请查看《6.6章节-Python3.x环境安装配置》。
注意：集群中所有节点都要升级为相同的python3.x版本的环境。

7、升级类型检查

omm用户下，执行gs_upgradectl命令检查升级类型。systable-upgrade为离线小版本升级，binary-upgrade为离线二进制升级。本次升级为离线小版本升级。

[root@gsdb11 ~]# su - omm
[omm@gsdb11 ~]$ gs_upgradectl -t upgrade-type -X /software/gaussdb/clusterconfig.xml
Checking upgrade type.
Successfully checked upgrade type.
Upgrade type: systable-upgrade.
[omm@gsdb11 ~]$
复制

8、执行升级

omm用户下，执行gs_upgradectl命令正式升级。

[omm@gsdb11 ~]$ gs_upgradectl -t offline-upgrade -X /software/gaussdb/clusterconfig.xml
Performing systable-upgrade.
Checking zengine parameters.
Successfully check zengine parameters.
Checking cluster health.
Successfully checked cluster health.
Checking database status.
Successfully checked database status.
Checking space for backup files.
Check need size of [/u01/gaussdb/temp/binary_upgrade] in [gsdb11] is [48580526080 Byte].
Check need size of [/u01/gaussdb/temp/binary_upgrade] in [gsdb12] is [49486495744 Byte].
Check need size of [/u01/gaussdb/temp/binary_upgrade] in [gsdb13] is [49486495744 Byte].
Check need size of [/u01/gaussdb/temp/binary_upgrade] in [gsdb14] is [49486495744 Byte].
Successfully checked space for backup files.
Change the primary dn and cn to read only status.
Successfully changed the primary dn and cn to read only status.
Checking database read only status.
Successfully checked database read only status.
Checking sync info for dns.
Successfully checking sync info for dns.
Generating upgrade sql file.
Successfully generated upgrade sql file.
Generating combined upgrade sql file.
Successfully generated combined upgrade sql file.
Backing up current application and configurations.
Checking ztools path in each host.
Successfully checked ztools path in each host.
Successfully backed up current application and configurations.
Successfully record protection mode
Saving system tabls path.
Successfully saved system tables path.
Saving redo log file path.
Successfully saved redolog file path.
Saving undo log file path.
Successfully saved redolog file path.
Stopping the cluster.
Successfully stopped the cluster.
Stopping the etcd and agent.
Successfully stopped the etcd and agent.
Update etcd keys.
Successfully update etcd keys.
Starting all dns to open status for backuping system cntl and redolog.
Successfully started all dns to open status for backuping system cntl and redolog.
Backing up current system tables.
Successfully backed up system tables.
Backing up current cntl files.
Successfully backed up cntl files.
Backing up current redolog files.
Successfully backed up redolog files.
Backing up current undolog files.
Successfully backed up undolog files.
Shutdowning all dns for backuping system cntl and redolog.
Successfully shutdown all dns for backuping system cntl and redolog.
Upgrading application.
Successfully upgraded application.
Starting the restrict mode cluster.
Successfully started the restrict mode cluster.
Upgrading the system table
Successfully upgraded the system table
Shutting down the restrict mode cluster
Successfully shut down the restrict mode cluster
Starting the cns, dns to open status.
Successfully started the cns, dns to open status.
Converting the cns, primary dns to read write status.
Successfully converted the cns, primary dns to read write status.
Shutting down the open status cns, dns.
Successfully shutted down the open status cns, dns.
Starting the etcd.
Successfully started the etcd.
Loading the json.
Successfully loaded the json.
Starting cm agent.
Successfully started cm agent.
Starting the cluster.
Successfully started the cluster.
Commit systable-upgrade succeeded.
Time for "UpgradeCheck" : 94.1546 seconds
Time for "UpgradeBackup" : 74.5531 seconds
Time for "UpgradeStopCluster" : 99.8998 seconds
Time for "UpgradeStopCluster" : 99.8998 seconds
Time for "UpgradeBackupSysCntlRedo" : 923.6309 seconds
Time for "Upgrade" : 14.0051 seconds
Time for "KernelUpgrade" : 258.2037 seconds
Time for "ShutdownRestrict" : 16.2235 seconds
Time for "StartOpen" : 29.6989 seconds
Time for "ConvertReadWrite" : 21.5191 seconds
Time for "ShutdownOpen" : 15.0699 seconds
Time for "SystemTable" : 523.5643 seconds
Time for "UpgradeStartCluster" : 59.3669 seconds
Time for "Total" : 1812.7166 seconds
[omm@gsdb11 ~]$
复制

9、升级后检查

检查集群状态：

[omm@gsdb11 ~]$ gs_om -t status
Set output to terminal.
--------------------------------------------------------------------Cluster Status--------------------------------------------------------------------
az_state :      single_az
cluster_state : Normal
balanced :      true
----------------------------------------------------------------------AZ Status-----------------------------------------------------------------------
AZ:AZ1                ROLE:primary            STATUS:ONLINE      
---------------------------------------------------------------------Host Status----------------------------------------------------------------------
HOST:gsdb11           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.126
HOST:gsdb12           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.127
HOST:gsdb13           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.128
HOST:gsdb14           AZ:AZ1                  STATUS:ONLINE       IP:192.168.179.129
----------------------------------------------------------------Cluster Manager Status----------------------------------------------------------------
INSTANCE:CM1          ROLE:slave              STATUS:ONLINE       HOST:gsdb11           ID:601
INSTANCE:CM2          ROLE:slave              STATUS:ONLINE       HOST:gsdb12           ID:602
INSTANCE:CM3          ROLE:slave              STATUS:ONLINE       HOST:gsdb13           ID:603
INSTANCE:CM4          ROLE:primary            STATUS:ONLINE       HOST:gsdb14           ID:604
---------------------------------------------------------------------ETCD Status----------------------------------------------------------------------
INSTANCE:ETCD1        ROLE:leader             STATUS:ONLINE       HOST:gsdb11           ID:701      PORT:2379         DataDir:/u01/gaussdb/data/etcd
INSTANCE:ETCD2        ROLE:follower           STATUS:ONLINE       HOST:gsdb12           ID:702      PORT:2379         DataDir:/u01/gaussdb/data/etcd
INSTANCE:ETCD3        ROLE:follower           STATUS:ONLINE       HOST:gsdb13           ID:703      PORT:2379         DataDir:/u01/gaussdb/data/etcd
----------------------------------------------------------------------CN Status-----------------------------------------------------------------------
INSTANCE:cn_401       ROLE:no role            STATUS:ONLINE       HOST:gsdb11           ID:401      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_402       ROLE:no role            STATUS:ONLINE       HOST:gsdb12           ID:402      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_403       ROLE:no role            STATUS:ONLINE       HOST:gsdb13           ID:403      PORT:8000         DataDir:/u01/gaussdb/data/cn
INSTANCE:cn_404       ROLE:no role            STATUS:ONLINE       HOST:gsdb14           ID:404      PORT:8000         DataDir:/u01/gaussdb/data/cn
---------------------------------------------------------Instances Status in Group (group_1)----------------------------------------------------------
INSTANCE:DB1_1        ROLE:standby            STATUS:ONLINE       HOST:gsdb11           ID:1        PORT:40000        DataDir:/u01/gaussdb/data/dn1
INSTANCE:DB1_2        ROLE:primary            STATUS:ONLINE       HOST:gsdb12           ID:2        PORT:40021        DataDir:/u01/gaussdb/data/dn1
---------------------------------------------------------Instances Status in Group (group_2)----------------------------------------------------------
INSTANCE:DB2_3        ROLE:primary            STATUS:ONLINE       HOST:gsdb12           ID:3        PORT:40000        DataDir:/u01/gaussdb/data/dn2
INSTANCE:DB2_4        ROLE:standby            STATUS:ONLINE       HOST:gsdb13           ID:4        PORT:40021        DataDir:/u01/gaussdb/data/dn2
---------------------------------------------------------Instances Status in Group (group_3)----------------------------------------------------------
INSTANCE:DB3_5        ROLE:primary            STATUS:ONLINE       HOST:gsdb13           ID:5        PORT:40000        DataDir:/u01/gaussdb/data/dn3
INSTANCE:DB3_6        ROLE:standby            STATUS:ONLINE       HOST:gsdb14           ID:6        PORT:40021        DataDir:/u01/gaussdb/data/dn3
---------------------------------------------------------Instances Status in Group (group_4)----------------------------------------------------------
INSTANCE:DB4_8        ROLE:standby            STATUS:ONLINE       HOST:gsdb11           ID:8        PORT:40021        DataDir:/u01/gaussdb/data/dn4
INSTANCE:DB4_7        ROLE:primary            STATUS:ONLINE       HOST:gsdb14           ID:7        PORT:40000        DataDir:/u01/gaussdb/data/dn4
-----------------------------------------------------------------------Manage IP----------------------------------------------------------------------
HOST:gsdb11           IP:192.168.179.126
HOST:gsdb12           IP:192.168.179.127
HOST:gsdb13           IP:192.168.179.128
HOST:gsdb14           IP:192.168.179.129
-------------------------------------------------------------------Query Action Info------------------------------------------------------------------
HOSTNAME: gsdb11     TIME: 2020-03-09 18:26:08.534200
------------------------------------------------------------------------Float Ip------------------------------------------------------------------
HOST:gsdb12    DB1_2:192.168.179.127    IP:
HOST:gsdb12    DB2_3:192.168.179.127    IP:
HOST:gsdb13    DB3_5:192.168.179.128    IP:
HOST:gsdb14    DB4_7:192.168.179.129    IP:
[omm@gsdb11 ~]$
复制

检查数据库版本：

[omm@gsdb11 ~]$ zsql omm/yhadmin_123@192.168.179.126:8000 -q

connected.

SQL> select * from v$version;

VERSION                                                         
----------------------------------------------------------------
GaussDB_T_1.0.2.B307 Release d4484ac                            
ZENGINE                                                         

2 rows fetched.

SQL> select name,status,open_status,database_role from v$database;

NAME                             STATUS               OPEN_STATUS          DATABASE_ROLE                 
-------------------------------- -------------------- -------------------- ------------------------------
YHDB                            OPEN                 READ WRITE           PRIMARY                       

1 rows fetched.

SQL> exit 

[omm@gsdb11 ~]$
复制

到此，GaussDB T 1.0.1分布式集群的升级完成。

10、升级失败后回滚

如果在升级过程中失败需要回滚，在omm用户下，执行gs_upgradectl命令回退。操作如下：

[omm@gsdb11 ~]$ gs_upgradectl -t offline-rollback -X /software/gaussdb/clusterconfig.xml
复制

gaussdb t

最后修改时间：2020-03-11 20:57:34

「喜欢这篇文章，您的关注和赞赏是给作者最好的鼓励」

关注作者

2人已赞赏

文章被以下合辑收录

走进华为云，走进鲲鹏，走进GaussDB（共20篇）

了解华为云和鲲鹏架构，学习GaussDB数据库

关注

获得了98次点赞

内容获得35次评论

获得了242次收藏

TA的专栏

一步一步学习OceanBase系列

收录28篇内容

Oracle 性能优化和故障诊断

收录5篇内容

走进华为云，走进鲲鹏，走进GaussDB

收录20篇内容

GaussDB T 分布式集群从1.0.1升级至1.0.2

分布式集群升级

1、 关于gs_upgradectl命令说明

2、 关于升级白名单

3、 离线升级注意事项

4、 升级前集群检查

4.1、 集群状态检查

4.2 检查数据库版本

4.3、 检查DN主备数据同步情况

5、 上传目标版本安装包

6、 升级预检查

7、 升级类型检查

8、 执行升级

9、 升级后检查

10、 升级失败后回滚