ITPub博客

首页 > 数据库 > 国内数据库 > 熟能生巧丨MogDB数据库+CM+VIP两节点集群升级

熟能生巧丨MogDB数据库+CM+VIP两节点集群升级

原创 国内数据库 作者:云和恩墨 时间:2024-08-12 15:46:42 0 删除 编辑
本文记录了 MogDB 5.0.5版本升级至5.0.7版本的全部过程,欢迎大家在非生产环境下动手跟练。

查看PTK版本


[root@mogdb1 ~]# ptk --version

PTK Version:    v1.4.6 release
Go Version:     go1.19.10
Build Date:     2024-05-28T11:00:47
Git Hash:       5723e886
OS/Arch:        linux/amd64
[root@mogdb1 ~]#

查看集群状态


[root@mogdb1 ~]# ptk cluster status -n ebhk 

[   Cluster State   ]
cluster_name                   : ebhk
cluster_state                  : Normal
database_version               : MogDB 5.0.5 (build b77f1a82)
cm_version                     : 5.0.5 (build 3a8b3616)
active_vip                     : 192.168.115.83

[  CMServer State   ]
 id |       ip       | port  |    hostname     |  role    
-----+----------------+-------+-----------------+----------
 1  | 192.168.115.81 | 15300 | mogdb1.mark.com | primary  
 2  | 192.168.115.82 | 15300 | mogdb2.mark.com | standby  

[  Datanode State   ]
 cluster_name |  id  |       ip       | port  | user | nodename | db_role | state  |  uptime  | upstream  
---------------+------+----------------+-------+------+----------+---------+--------+----------+-----------
 ebhk         | 6001 | 192.168.115.81 | 26000 | omm  | dn_6001  | primary | Normal | 00:01:01 | -        
              | 6002 | 192.168.115.82 | 26000 | omm  | dn_6002  | standby | Normal | 00:01:05 | -  

[root@mogdb1 ~]# ip a
1: lo:

升级PTK版本

注:MogDB v5.0.7要求PTK版本大等于1.4.7

[root@mogdb1 u01]# cd u01

[root@mogdb1 u01]# tar -xzvf ptk_1.5.2_linux_x86_64.tar.gz -C tmp/
CHANGELOG/.gitkeep
README.md
ptk
[root@mogdb1 u01]# which ptk
/root/.ptk/bin/ptk
[root@mogdb1 u01]# cp -a tmp/ptk root/.ptk/bin/
cp: overwrite ‘/root/.ptk/bin/ptk’? y
[root@mogdb1 u01]# ptk --version
PTK Version:    v1.5.2 release
Go Version:     go1.19.10
Build Date:     2024-06-18T10:23:48
Git Hash:       812d1612
OS/Arch:        linux/amd64
[root@mogdb1 u01]#

升级MogDB至5.0.7

01 卸载旧版本CM


[root@mogdb1 ~]# ptk cluster -n ebhk uninstall-cm

INFO[2024-06-23T20:18:30.705] [192.168.115.82][omm] remove cron task: om_monitor
INFO[2024-06-23T20:18:30.710] [192.168.115.81][omm] remove cron task: om_monitor
INFO[2024-06-23T20:18:30.784] [192.168.115.82][omm] kill user "omm" processes if exist: [om_monitor cm_agent cm_server fenced UDF]
INFO[2024-06-23T20:18:30.785] [192.168.115.81][omm] kill user "omm" processes if exist: [om_monitor cm_agent cm_server fenced UDF]
INFO[2024-06-23T20:18:30.835] [192.168.115.82][omm] remove files: u01/mogdb/app/bin/om_monitor*,/u01/mogdb/app/bin/cm_agent*,/u01/mogdb/app/bin/cm_server*,/u01/mogdb/app/bin/cm_ctl*,/u01/mogdb/app/bin/cm_persist*,/u01/mogdb/app/bin/*manual*start*,/u01/mogdb/app/bin/promote_mode_cms
INFO[2024-06-23T20:18:30.846] [192.168.115.81][omm] remove files: u01/mogdb/app/bin/om_monitor*,/u01/mogdb/app/bin/cm_agent*,/u01/mogdb/app/bin/cm_server*,/u01/mogdb/app/bin/cm_ctl*,/u01/mogdb/app/bin/cm_persist*,/u01/mogdb/app/bin/*manual*start*,/u01/mogdb/app/bin/promote_mode_cms
INFO[2024-06-23T20:18:30.896] [192.168.115.82][omm] remove files: u01/mogdb/log/cm,/u01/mogdb/app/share/sslcert/cm,/u01/mogdb/cm/cm_server,/u01/mogdb/cm/cm_agent,/u01/mogdb/cm/dcf_data,/u01/mogdb/cm/gstor
INFO[2024-06-23T20:18:30.905] [192.168.115.81][omm] remove files: u01/mogdb/log/cm,/u01/mogdb/app/share/sslcert/cm,/u01/mogdb/cm/cm_server,/u01/mogdb/cm/cm_agent,/u01/mogdb/cm/dcf_data,/u01/mogdb/cm/gstor
INFO[2024-06-23T20:18:30.953] [192.168.115.82][omm] clear cm dir          
INFO[2024-06-23T20:18:30.962] [192.168.115.81][omm] clear cm dir          
INFO[2024-06-23T20:18:31.003] [192.168.115.82][omm] generate cluster_static_config file
INFO[2024-06-23T20:18:31.011] [192.168.115.81][omm] generate cluster_static_config file
INFO[2024-06-23T20:18:31.140] uninstall succeeded                          
INFO[2024-06-23T20:18:31.140] time elapsed: 0s

02 卸载CM后的状态


[root@mogdb1 ~]# ptk cluster status -n ebhk 

[   Cluster State   ]
cluster_name                   : ebhk
cluster_state                  : Normal
database_version               : MogDB 5.0.5 (build b77f1a82)

[  Datanode State   ]
 cluster_name |  id  |       ip       | port  | user | nodename | db_role | state  |  uptime  | upstream  
---------------+------+----------------+-------+------+----------+---------+--------+----------+-----------
 ebhk         | 6001 | 192.168.115.81 | 26000 | omm  | dn_6001  | primary | Normal | 00:02:57 | -        
              | 6002 | 192.168.115.82 | 26000 | omm  | dn_6002  | standby | Normal | 00:03:01 | -        
[root@mogdb1 ~]# ip a
1: lo:

03 升级MogDB数据库集群


[root@mogdb1 ~]# ptk cluster -n ebhk upgrade -p u01/MogDB-5.0.7-CentOS-x86_64-all.tar.gz

INFO[2024-06-23T20:20:18.120] PTK Version: 1.5.2 release                  
INFO[2024-06-23T20:20:18.127] new step recorder, current step: "start"    
Tip:
       The upgrade process relies on SSH.
       Please ensure that the network is always worked
       during the upgrade process.
INFO[2024-06-23T20:20:18.128] parsing package from u01/MogDB-5.0.7-CentOS-x86_64-all.tar.gz
INFO[2024-06-23T20:20:26.022] kernel package name: MogDB-5.0.7-CentOS-64bit.tar.gz
INFO[2024-06-23T20:20:26.022] package version: MogDB-5.0.7,92.924,c4707384
INFO[2024-06-23T20:20:26.022] check db version                            
INFO[2024-06-23T20:20:26.022] big upgrade: true                            
INFO[2024-06-23T20:20:26.022] current version: 5.0.5, target version: 5.0.7
INFO[2024-06-23T20:20:26.022] current number: 92.901, target number: 92.924
INFO[2024-06-23T20:20:26.207] version is ok                                
INFO[2024-06-23T20:20:26.208] prepare all upgrade sql                      
INFO[2024-06-23T20:20:26.954] extract upgrade_sql.tar.gz successfully      
INFO[2024-06-23T20:20:27.190] no created plugins found                    
INFO[2024-06-23T20:20:27.209] create temp dir                              
INFO[2024-06-23T20:20:27.228] upload upgrade_extensions.tar.gz            
INFO[2024-06-23T20:20:27.250] extract upgrade_extensions.tar.gz to dir u01/mogdb/tmp/upgrade
INFO[2024-06-23T20:20:27.439] check cluster status                        
INFO[2024-06-23T20:20:27.616] cluster state is ok                          
INFO[2024-06-23T20:20:27.867] create remote temporary upgrade directory    
✔ PTK will set cluster to readonly and restart cluster during upgrade, are you ready (default=n) [y/n]: y
INFO[2024-06-23T20:20:35.229] set upgrade_mode to 2                        
INFO[2024-06-23T20:20:35.271] set cluster readonly                        
INFO[2024-06-23T20:20:35.319] check disk size                              
INFO[2024-06-23T20:20:35.442] check and wait xlog sync                    
INFO[2024-06-23T20:20:35.488] setting temporary guc values                
INFO[2024-06-23T20:20:35.488] set guc param support_extended_features value to "on"
INFO[2024-06-23T20:20:35.522] set guc param enable_wdr_snapshot value to "off"
INFO[2024-06-23T20:20:35.563] stop all datanodes                          
INFO[2024-06-23T20:20:35.563] operation: stop                              
INFO[2024-06-23T20:20:35.563] ========================================    
INFO[2024-06-23T20:20:35.627] stop db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:20:36.661] stop db [192.168.115.82:26000] successfully  
INFO[2024-06-23T20:20:36.744] stop db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:20:38.779] stop db [192.168.115.81:26000] successfully  
INFO[2024-06-23T20:20:38.779] ========================================    
INFO[2024-06-23T20:20:38.779] stop successfully                            
INFO[2024-06-23T20:20:38.780] backup old app and tool                      
INFO[2024-06-23T20:20:51.116] checking cluster state before start          
INFO[2024-06-23T20:20:51.186] operation: start                            
INFO[2024-06-23T20:20:51.186] ========================================    
INFO[2024-06-23T20:20:51.186] start db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:20:53.326] start db [192.168.115.81:26000] successfully
INFO[2024-06-23T20:20:53.326] start db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:20:56.071] start db [192.168.115.82:26000] successfully
INFO[2024-06-23T20:20:56.297] ========================================    
INFO[2024-06-23T20:20:56.298] start cluster successfully                  
INFO[2024-06-23T20:20:56.413] call hook script: before_pre_upgrade_script  
INFO[2024-06-23T20:20:57.105] execute rollback sql                        
INFO[2024-06-23T20:20:57.105] execute rollback sql on postgres            
INFO[2024-06-23T20:20:57.373] execute rollback sql on otherdb: [template1 template0], parallel num: 10
INFO[2024-06-23T20:20:57.665] execute upgrade sql                          
INFO[2024-06-23T20:20:57.665] execute upgrade sql on postgres              
INFO[2024-06-23T20:20:57.889] execute upgrade sql on otherdb: [template1 template0], parallel num: 10
INFO[2024-06-23T20:20:58.120] execute checkpoint                          
INFO[2024-06-23T20:20:58.481] call hook script: after_pre_upgrade_script  
INFO[2024-06-23T20:20:58.520] stop all datanodes                          
INFO[2024-06-23T20:20:58.520] operation: stop                              
INFO[2024-06-23T20:20:58.520] ========================================    
INFO[2024-06-23T20:20:58.617] stop db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:21:01.683] stop db [192.168.115.82:26000] successfully  
INFO[2024-06-23T20:21:01.784] stop db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:21:02.826] stop db [192.168.115.81:26000] successfully  
INFO[2024-06-23T20:21:02.826] ========================================    
INFO[2024-06-23T20:21:02.826] stop successfully                            
INFO[2024-06-23T20:21:02.827] check need update config in postgresql.conf  
INFO[2024-06-23T20:21:02.827] backup old configs                          
INFO[2024-06-23T20:21:02.875] install new package files                    
INFO[2024-06-23T20:21:02.875] extract new package locally                  
INFO[2024-06-23T20:21:03.828] distribute new package files to all datanodes
INFO[2024-06-23T20:21:03.828] [192.168.115.81][omm] upload kernel package...
INFO[2024-06-23T20:21:03.829] [192.168.115.82][omm] upload kernel package...
INFO[2024-06-23T20:21:06.735] [192.168.115.81][omm] upload om package...  
INFO[2024-06-23T20:21:07.028] [192.168.115.81][omm] upload cm package...  
INFO[2024-06-23T20:21:09.403] [192.168.115.82][omm] upload om package...  
INFO[2024-06-23T20:21:10.336] [192.168.115.82][omm] upload cm package...  
INFO[2024-06-23T20:21:12.249] [192.168.115.81][omm] validate and try to fix ld library for gs_initdb
INFO[2024-06-23T20:21:12.283] [192.168.115.81][omm] validate and try to fix ld library for mogdb
INFO[2024-06-23T20:21:12.318] [192.168.115.81][omm] try to fix psutil python lib
INFO[2024-06-23T20:21:12.396] [192.168.115.81][omm] write file u01/mogdb/tool/script/py_pstree.py
INFO[2024-06-23T20:21:15.341] [192.168.115.82][omm] validate and try to fix ld library for gs_initdb
INFO[2024-06-23T20:21:15.383] [192.168.115.82][omm] validate and try to fix ld library for mogdb
INFO[2024-06-23T20:21:15.429] [192.168.115.82][omm] try to fix psutil python lib
INFO[2024-06-23T20:21:15.509] [192.168.115.82][omm] write file u01/mogdb/tool/script/py_pstree.py
INFO[2024-06-23T20:21:15.639] update upgrade_version                      
INFO[2024-06-23T20:21:15.670] restore old configs to new app              
INFO[2024-06-23T20:21:15.711] delete deprecated guc                        
INFO[2024-06-23T20:21:15.891] update config in postgresql.conf            
INFO[2024-06-23T20:21:15.892] start with old number                        
INFO[2024-06-23T20:21:15.892] checking cluster state before start          
INFO[2024-06-23T20:21:15.972] operation: start                            
INFO[2024-06-23T20:21:15.972] ========================================    
INFO[2024-06-23T20:21:15.972] start db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:21:18.258] start db [192.168.115.81:26000] successfully
INFO[2024-06-23T20:21:18.258] start db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:21:20.458] start db [192.168.115.82:26000] successfully
INFO[2024-06-23T20:21:20.731] ========================================    
INFO[2024-06-23T20:21:20.731] start cluster successfully                  
INFO[2024-06-23T20:21:20.732] call hook script: before_post_upgrade_script
INFO[2024-06-23T20:21:20.762] checking cluster status                      
INFO[2024-06-23T20:21:21.154] cluster status is normal                    
INFO[2024-06-23T20:21:21.154] execute rollback-post sql                    
INFO[2024-06-23T20:21:21.154] execute rollback-post sql on postgres        
INFO[2024-06-23T20:21:21.447] execute rollback-post sql on otherdb: [template1 template0], parallel num: 10
INFO[2024-06-23T20:21:21.824] execute upgrade-post sql                    
INFO[2024-06-23T20:21:21.824] execute upgrade-post sql on postgres        
INFO[2024-06-23T20:21:22.114] execute upgrade-post sql on otherdb: [template1 template0], parallel num: 10
INFO[2024-06-23T20:21:22.420] call hook script: after_post_upgrade_script  
INFO[2024-06-23T20:21:22.454] after_post_upgrade_script output:
This version of whale doesn't support upgrade
INFO[2024-06-23T20:21:22.455] restore guc value                            
INFO[2024-06-23T20:21:22.455] restore guc param support_extended_features value to "off"
INFO[2024-06-23T20:21:22.499] restore guc param enable_wdr_snapshot value to "on"
INFO[2024-06-23T20:21:22.564] stop all datanodes                          
INFO[2024-06-23T20:21:22.564] operation: stop                              
INFO[2024-06-23T20:21:22.564] ========================================    
INFO[2024-06-23T20:21:22.677] stop db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:21:25.722] stop db [192.168.115.82:26000] successfully  
INFO[2024-06-23T20:21:25.834] stop db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:21:29.892] stop db [192.168.115.81:26000] successfully  
INFO[2024-06-23T20:21:29.892] ========================================    
INFO[2024-06-23T20:21:29.893] stop successfully                            
INFO[2024-06-23T20:21:29.893] start all datanodes                          
INFO[2024-06-23T20:21:29.893] checking cluster state before start          
INFO[2024-06-23T20:21:29.986] operation: start                            
INFO[2024-06-23T20:21:29.986] ========================================    
INFO[2024-06-23T20:21:29.986] start db [192.168.115.81:26000] ...          
INFO[2024-06-23T20:21:31.199] start db [192.168.115.81:26000] successfully
INFO[2024-06-23T20:21:31.199] start db [192.168.115.82:26000] ...          
INFO[2024-06-23T20:21:33.347] start db [192.168.115.82:26000] successfully
INFO[2024-06-23T20:21:33.574] wait following dn to Normal:                
INFO[2024-06-23T20:21:33.574] dn: 192.168.115.82 state: Catchup            
INFO[2024-06-23T20:21:36.814] ========================================    
INFO[2024-06-23T20:21:36.814] start cluster successfully                  
INFO[2024-06-23T20:21:36.815] upgrade successfully                        

If you confirm that the upgrade is correct, you can run this command to finish the upgrade:
   ptk cluster -n ebhk upgrade-commit
If you want to rollback the upgrade, you can run:
   ptk cluster -n ebhk upgrade-rollback
INFO[2024-06-23T20:21:36.815] time elapsed: 1m19s                          
[root@mogdb1 ~]#

04 提交MogDB数据库集群的升级


[root@mogdb1 ~]# ptk cluster -n ebhk upgrade-commit

INFO[2024-06-23T20:22:40.746] PTK Version: 1.5.2 release                  
INFO[2024-06-23T20:22:40.754] new step recorder, current step: "restart_dn_finally"
INFO[2024-06-23T20:22:40.754] check cluster status                        
INFO[2024-06-23T20:22:40.755] checking cluster status                      
INFO[2024-06-23T20:22:41.100] cluster status is normal                    
INFO[2024-06-23T20:22:41.297] set upgrade_mode to 0                        
INFO[2024-06-23T20:22:41.353] enable cluster read-write                    
INFO[2024-06-23T20:22:41.456] create temp dir                              
INFO[2024-06-23T20:22:41.479] upload upgrade_extensions.tar.gz            
INFO[2024-06-23T20:22:41.509] extract upgrade_extensions.tar.gz to dir u01/mogdb/tmp/upgrade
INFO[2024-06-23T20:22:41.758] call hook script: on_commit_script          
INFO[2024-06-23T20:22:41.804] clear temporary directories                  
INFO[2024-06-23T20:22:42.106] commit success                              
INFO[2024-06-23T20:22:42.106] time elapsed: 1s                            
[root@mogdb1 ~]

05 MogDB升级后集群状态


[root@mogdb1 ~]# ptk cluster status -n ebhk 

[   Cluster State   ]
cluster_name                   : ebhk
cluster_state                  : Normal
database_version               : MogDB 5.0.7 (build c4707384)

[  Datanode State   ]
 cluster_name |  id  |       ip       | port  | user | nodename | db_role | state  |  uptime  | upstream  
---------------+------+----------------+-------+------+----------+---------+--------+----------+-----------
 ebhk         | 6001 | 192.168.115.81 | 26000 | omm  | dn_6001  | primary | Normal | 00:02:09 | -        
              | 6002 | 192.168.115.82 | 26000 | omm  | dn_6002  | standby | Normal | 00:02:08 | -        
[root@mogdb1 ~]# ip a
1: lo:

06 安装新版CM集群


[root@mogdb1 ~]# ptk cluster -n ebhk install-cm ebhk -p  u01/MogDB-5.0.7-CentOS-x86_64-all.tar.gz

INFO[2024-06-23T20:25:43.523] cm enabled but cm_servers is empty, use db servers as cm servers
The cluster will contains 2 cm nodes, so please confirm following cms configs:
- (Optional) db_service_vip="192.168.115.83"
- (Required) third_party_gateway_ip="192.168.115.2"
- (Optional) cms_enable_failover_on2nodes="True"
- (Optional) cms_enable_db_crash_recovery="False"
Now, these configs are:
- db_service_vip="192.168.115.83"
- third_party_gateway_ip="192.168.115.2"
- cms_enable_failover_on2nodes="True"
- cms_enable_db_crash_recovery="False"
✔ Do you want to modify them (default=n) [y/n]: n
INFO[2024-06-23T20:25:52.166] check cluster state                          
INFO[2024-06-23T20:25:52.423] current cluster state: Normal                
INFO[2024-06-23T20:25:52.423] [192.168.115.81][omm] check cm_server port: 15300
INFO[2024-06-23T20:25:52.423] [192.168.115.82][omm] check cm_server port: 15300
INFO[2024-06-23T20:25:52.512] check the package from command line          
INFO[2024-06-23T20:25:52.512] parse package: "/u01/MogDB-5.0.7-CentOS-x86_64-all.tar.gz"
INFO[2024-06-23T20:25:59.618] compare cm package version with cluster version
INFO[2024-06-23T20:26:00.301] extract MogDB-5.0.7-CentOS-64bit-cm.tar.gz to dir tmp/tmp.USJnvgUraq
INFO[2024-06-23T20:26:00.493] execute command: cm_ctl --version | awk '{print $2,$4}'
INFO[2024-06-23T20:26:00.562] got cm version is MogDB-5.0.7                
INFO[2024-06-23T20:26:00.562] distributing cm package...                  
INFO[2024-06-23T20:26:01.351] generate ssl files for cm                    
INFO[2024-06-23T20:26:02.893] distribute ssl files                        
INFO[2024-06-23T20:26:03.204] [192.168.115.81][omm] add user omm to cron.allow
INFO[2024-06-23T20:26:03.204] [192.168.115.82][omm] add user omm to cron.allow
INFO[2024-06-23T20:26:03.211] [192.168.115.81][omm] create file cluster_manual_start
INFO[2024-06-23T20:26:03.232] [192.168.115.81][omm] make user omm's dir(s): u01/mogdb/cm,/u01/mogdb/cm/cm_server,/u01/mogdb/cm/cm_agent,/u01/mogdb/log/cm/om_monitor
INFO[2024-06-23T20:26:03.318] [192.168.115.82][omm] create file cluster_manual_start
INFO[2024-06-23T20:26:03.342] [192.168.115.82][omm] make user omm's dir(s): u01/mogdb/cm,/u01/mogdb/cm/cm_server,/u01/mogdb/cm/cm_agent,/u01/mogdb/log/cm/om_monitor
INFO[2024-06-23T20:26:03.820] [192.168.115.81][omm] extract MogDB-5.0.7-CentOS-64bit-cm.tar.gz to dir u01/mogdb/app
INFO[2024-06-23T20:26:03.929] [192.168.115.82][omm] extract MogDB-5.0.7-CentOS-64bit-cm.tar.gz to dir u01/mogdb/app
INFO[2024-06-23T20:26:04.029] [192.168.115.81][omm] change u01/mogdb/app owner to omm
INFO[2024-06-23T20:26:04.029] [192.168.115.81][omm] copy u01/mogdb/app/share/config/cm_server.conf.sample to u01/mogdb/cm/cm_server/cm_server.conf
INFO[2024-06-23T20:26:04.049] [192.168.115.81][omm] copy u01/mogdb/app/share/config/cm_agent.conf.sample to u01/mogdb/cm/cm_agent/cm_agent.conf
INFO[2024-06-23T20:26:04.069] [192.168.115.81][omm] copy u01/mogdb/app/script/cm_manage_vip.py to u01/mogdb/app/bin
INFO[2024-06-23T20:26:04.089] [192.168.115.81][omm] change u01/mogdb/cm owner to omm
INFO[2024-06-23T20:26:04.089] [192.168.115.81][omm] update cm config file: u01/mogdb/cm/cm_agent/cm_agent.conf
INFO[2024-06-23T20:26:04.128] [192.168.115.82][omm] change u01/mogdb/app owner to omm
INFO[2024-06-23T20:26:04.128] [192.168.115.82][omm] copy u01/mogdb/app/share/config/cm_server.conf.sample to u01/mogdb/cm/cm_server/cm_server.conf
INFO[2024-06-23T20:26:04.141] [192.168.115.81][omm] update cm config file: u01/mogdb/cm/cm_server/cm_server.conf
INFO[2024-06-23T20:26:04.151] [192.168.115.82][omm] copy u01/mogdb/app/share/config/cm_agent.conf.sample to u01/mogdb/cm/cm_agent/cm_agent.conf
INFO[2024-06-23T20:26:04.173] [192.168.115.82][omm] copy u01/mogdb/app/script/cm_manage_vip.py to u01/mogdb/app/bin
INFO[2024-06-23T20:26:04.194] [192.168.115.82][omm] change u01/mogdb/cm owner to omm
INFO[2024-06-23T20:26:04.194] [192.168.115.82][omm] update cm config file: u01/mogdb/cm/cm_agent/cm_agent.conf
INFO[2024-06-23T20:26:04.226] [192.168.115.81][omm] generate cluster_static_config file
INFO[2024-06-23T20:26:04.251] [192.168.115.82][omm] update cm config file: u01/mogdb/cm/cm_server/cm_server.conf
INFO[2024-06-23T20:26:04.321] [192.168.115.81][omm] start om_monitor      
INFO[2024-06-23T20:26:04.351] [192.168.115.82][omm] generate cluster_static_config file
INFO[2024-06-23T20:26:04.352] [192.168.115.81][omm] remove cron task: om_monitor
INFO[2024-06-23T20:26:04.379] [192.168.115.81][omm] set omm cron task: om_monitor
INFO[2024-06-23T20:26:04.403] [192.168.115.82][omm] start om_monitor      
INFO[2024-06-23T20:26:04.432] [192.168.115.82][omm] remove cron task: om_monitor
INFO[2024-06-23T20:26:04.460] [192.168.115.82][omm] set omm cron task: om_monitor
INFO[2024-06-23T20:26:04.508] starting cm servers with cm_ctl              
INFO[2024-06-23T20:26:12.337] start successfully                          
INFO[2024-06-23T20:26:12.337] install finished                            
[root@mogdb1 ~]#

07 安装新版CM后集群状态


[root@mogdb1 ~]# ptk cluster status -n ebhk 

[   Cluster State   ]
cluster_name                   : ebhk
cluster_state                  : Normal
database_version               : MogDB 5.0.7 (build c4707384)
cm_version                     : 5.0.7 (build 39e2ce35)

[  CMServer State   ]
 id |       ip       | port  |    hostname     |  role    
-----+----------------+-------+-----------------+----------
 1  | 192.168.115.81 | 15300 | mogdb1.mark.com | primary  
 2  | 192.168.115.82 | 15300 | mogdb2.mark.com | standby  

[  Datanode State   ]
 cluster_name |  id  |       ip       | port  | user | nodename | db_role | state  |  uptime  | upstream  
---------------+------+----------------+-------+------+----------+---------+--------+----------+-----------
 ebhk         | 6001 | 192.168.115.81 | 26000 | omm  | dn_6001  | primary | Normal | 00:06:28 | -        
              | 6002 | 192.168.115.82 | 26000 | omm  | dn_6002  | standby | Normal | 00:06:26 | -        
[root@mogdb1 ~]# ip a
1: lo:

08 载入cm-vip


[root@mogdb1 ~]# ptk cluster -n ebhk load-cm-vip --vip 192.168.115.83 --action install  --log-level debug

DEBU[2024-06-23T20:29:18.621] cmd: ptk cluster -n ebhk load-cm-vip --vip 192.168.115.83 --action install --log-level debug
DEBU[2024-06-23T20:29:18.623] tidy config successfully                    
DEBU[2024-06-23T20:29:18.623] [192.168.115.81][omm] new sudo user executor with config option:

注:因VIP 192.168.115.83还处在可ping通、被占用的状态,载入cm-vip操作失败。

09 删除已占用的cm-vip


[root@mogdb1 ~]# ifconfig -a

ens33: flags=4163

10 重新载入cm-vip


[root@mogdb1 ~]# ptk cluster -n ebhk load-cm-vip --vip 192.168.115.83 --action install  --log-level debug

DEBU[2024-06-23T20:42:33.183] cmd: ptk cluster -n ebhk load-cm-vip --vip 192.168.115.83 --action install --log-level debug
DEBU[2024-06-23T20:42:33.184] tidy config successfully                    
DEBU[2024-06-23T20:42:33.185] [192.168.115.81][omm] new sudo user executor with config option:

11 查询集群状态,确认CM版本及vip已激活


[root@mogdb1 ~]# ptk cluster status -n ebhk 

[   Cluster State   ]
cluster_name                   : ebhk
cluster_state                  : Normal
database_version               : MogDB 5.0.7 (build c4707384)
cm_version                     : 5.0.7 (build 39e2ce35)
active_vip                     : 192.168.115.83

[  CMServer State   ]
 id |       ip       | port  |    hostname     |  role    
-----+----------------+-------+-----------------+----------
 1  | 192.168.115.81 | 15300 | mogdb1.mark.com | primary  
 2  | 192.168.115.82 | 15300 | mogdb2.mark.com | standby  

[  Datanode State   ]
 cluster_name |  id  |       ip       | port  | user | nodename | db_role | state  |  uptime  | upstream  
---------------+------+----------------+-------+------+----------+---------+--------+----------+-----------
 ebhk         | 6001 | 192.168.115.81 | 26000 | omm  | dn_6001  | primary | Normal | 00:00:53 | -        
              | 6002 | 192.168.115.82 | 26000 | omm  | dn_6002  | standby | Normal | 00:00:53 | -        
[root@mogdb1 ~]# ip a
1: lo:


来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/29715045/viewspace-3024791/ ,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2014-06-19

  • 博文量
    183
  • 访问量
    346684