南大通用数据库-Gbase-8a-学习-06-集群节点扩容（8.6版本）

已于 2022-08-18 16:28:39 修改
阅读量604 收藏 2
点赞数 2
分类专栏： # Gbase-8a-学习 文章标签： 数据库 学习 linux dba 运维
于 2022-08-12 11:00:41 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_45111959/article/details/126288226
版权

一、测试环境

名称值
cpuIntel® Core™ i5-1035G1 CPU @ 1.00GHz
操作系统CentOS Linux release 7.9.2009 (Core)
内存4G
逻辑核数3
原有节点1-IP192.168.142.10
扩容节点2-IP192.168.142.11
数据库版本8.6.2.43-R33.132743

二、操作步骤

1、查看集群状态

[root@localhost ~]# gcadmin
CLUSTER STATE:  ACTIVE
CLUSTER MODE:   NORMAL

=====================================================================
|               GBASE COORDINATOR CLUSTER INFORMATION               |
=====================================================================
|   NodeName   |       IpAddress       |gcware |gcluster |DataState |
---------------------------------------------------------------------
| coordinator1 |    192.168.142.10     | OPEN  |  OPEN   |    0     |
---------------------------------------------------------------------
=================================================================
|                GBASE DATA CLUSTER INFORMATION                 |
=================================================================
|NodeName |       IpAddress       |gnode |syncserver |DataState |
-----------------------------------------------------------------
|  node1  |    192.168.142.10     | OPEN |   OPEN    |    0     |
-----------------------------------------------------------------

2、关闭集群

由于我们需要添加管理节点，所以必须要关闭所有节点服务，如果只添加数据节点，可以不停止服务。添加管理节点，不停服务，报错如下：

some gcluster process still running on host 192.168.142.10, use 'pidof gclusterd gbased corosync gcmonit gcrecover gc_sync_server;' to check.
Must stop all gcluster nodes before extend gcluster. you can search 'still running' in gcinstall.log to find them.

每个节点都需要执行。

[root@localhost ~]# service gcware stop
Stopping GCMonit success!
Signaling GCRECOVER (gcrecover) to terminate:              [  确定  ]
Waiting for gcrecover services to unload:....              [  确定  ]
Signaling GCSYNC (gc_sync_server) to terminate:            [  确定  ]
Waiting for gc_sync_server services to unload:             [  确定  ]
Signaling GCLUSTERD  to terminate:                         [  确定  ]
Waiting for gclusterd services to unload:........          [  确定  ]
Signaling GBASED  to terminate:                            [  确定  ]
Waiting for gbased services to unload:....                 [  确定  ]
Signaling GCWARE (gcware) to terminate:                    [  确定  ]
Waiting for gcware services to unload:.                    [  确定  ]

3、查看集群进程是否关闭

每个节点都可以看一下，建议看，不看也OK。

[root@localhost ~]# ps -ef|grep gbase
root       4177   3591  0 16:43 pts/0    00:00:00 grep --color=auto gbase

4、修改配置文件demo.options

[root@localhost gcluster]# cd /opt/pkg/gcinstall/

[root@localhost gcinstall]# ll
总用量 93272
-rwxrwxrwx. 1 root  root       435 8月   7 20:27 192.168.142.10.options
-rwxrwxrwx. 1 root  root       435 8月   7 20:27 192.168.142.11.options
-rw-r--r--. 1 gbase gbase      292 12月 17 2021 BUILDINFO
-rw-r--r--. 1 gbase gbase  2249884 12月 17 2021 bundle_data.tar.bz2
-rw-r--r--. 1 gbase gbase 87478657 12月 17 2021 bundle.tar.bz2
-rw-r--r--. 1 gbase gbase     1951 12月 17 2021 CGConfigChecker.py
-rw-r--r--. 1 root  root      1895 8月   7 20:27 CGConfigChecker.pyc
-rw-r--r--. 1 gbase gbase      309 12月 17 2021 cluster.conf
-rwxr-xr-x. 1 gbase gbase     4167 12月 17 2021 CorosyncConf.py
-rw-r--r--. 1 gbase gbase      420 8月   7 20:26 demo.options
-rw-r--r--. 1 gbase gbase      154 12月 17 2021 dependRpms
-rw-r--r--. 1 gbase gbase      684 12月 17 2021 example.xml
-rwxr-xr-x. 1 gbase gbase      419 12月 17 2021 extendCfg.xml
-rw-r--r--. 1 gbase gbase      781 12月 17 2021 FileCheck.py
-rw-r--r--. 1 root  root      1173 8月   7 20:27 FileCheck.pyc
-rw-r--r--. 1 gbase gbase     2700 12月 17 2021 fulltext.py
-rw-r--r--. 1 gbase gbase  4818440 12月 17 2021 gbase_data_timezone.sql
-rw-r--r--. 1 gbase gbase      137 8月   7 20:29 gcChangeInfo.xml
-rwxrw-rw-. 1 root  root     13109 8月   7 20:29 gcinstall.log
-rwxr-xr-x. 1 gbase gbase    76282 12月 17 2021 gcinstall.py
-rwxrwxrwx. 1 gbase gbase     3362 12月 17 2021 GetOSType.py
-rw-r--r--. 1 gbase gbase   156505 12月 17 2021 InstallFuns.py
-rw-r--r--. 1 root  root    126295 8月   7 20:27 InstallFuns.pyc
-rw-r--r--. 1 gbase gbase   237364 12月 17 2021 InstallTar.py
-rw-r--r--. 1 gbase gbase     1114 12月 17 2021 license.txt
-rwxr-xr-x. 1 gbase gbase      296 12月 17 2021 loginUserPwd.json
-rwxr-xr-x. 1 gbase gbase    75990 12月 17 2021 pexpect.py
-rw-r--r--. 1 root  root     63064 8月   7 20:27 pexpect.pyc
-rwxr-xr-x. 1 gbase gbase    25093 12月 17 2021 replace.py
-rw-r--r--. 1 gbase gbase     1715 12月 17 2021 RestoreLocal.py
-rwxr-xr-x. 1 gbase gbase     6622 12月 17 2021 Restore.py
-rw-r--r--. 1 gbase gbase     7312 12月 17 2021 rmt.py
-rw-r--r--. 1 root  root      5625 8月   7 20:27 rmt.pyc
-rwxr-xr-x. 1 gbase gbase      296 12月 17 2021 rootPwd.json
-rw-r--r--. 1 gbase gbase     2717 12月 17 2021 SSHThread.py
-rw-r--r--. 1 root  root      3823 8月   7 20:27 SSHThread.pyc
-rwxr-xr-x. 1 gbase gbase    21710 12月 17 2021 unInstall.py
-rw-r--r--. 1 root  root     17079 8月   7 20:27 unInstall.pyc

[root@localhost gcinstall]# cat demo.options 
installPrefix= /opt
coordinateHost = 192.168.142.11
coordinateHostNodeID = 234,235,237
dataHost = 192.168.142.11
existCoordinateHost = 192.168.142.10
existDataHost = 192.168.142.10
loginUser= root
loginUserPwd = 'qwer1234'
#loginUserPwdFile = loginUserPwd.json
dbaUser = gbase
dbaGroup = gbase
dbaPwd = 'gbase'
rootPwd = 'qwer1234'
#rootPwdFile = rootPwd.json
dbRootPwd = ''
#mcastAddr = 226.94.1.39
mcastPort = 5493

5、安装数据库服务

[root@localhost gcinstall]# su - gbase
上一次登录：五 8月 12 09:10:09 CST 2022pts/2 上

[gbase@localhost gcinstall]$ ./gcinstall.py --silent=demo.options
*********************************************************************************
Thank you for choosing GBase product!


Please read carefully the following licencing agreement before installing GBase product:
TIANJIN GENERAL DATA TECHNOLOGY CO., LTD. LICENSE AGREEMENT
 
READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSETERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWAREMEDIA PACKAGE.  BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO THE TERMS OF THIS AGREEMENT.  IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS.  IF YOU DO NOT AGREE TO ALL THESE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND.
 

1.  CHINESE GOVERNMENT RESTRICTED.  If Software is being acquired by or on behalf of the Chinese Government , then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement.
 
2.  GOVERNING LAW.  Any action related to this Agreement will be governed by Chinese law: "COPYRIGHT LAW OF THE PEOPLE'S REPUBLIC OF CHINA","PATENT LAW OF THE PEOPLE'S REPUBLIC OF CHINA","TRADEMARK LAW OF THE PEOPLE'S REPUBLIC OF CHINA","COMPUTER SOFTWARE PROTECTION REGULATIONS OF THE PEOPLE'S REPUBLIC OF CHINA".  No choice of law rules of any jurisdiction will apply."
 

*********************************************************************************
Do you accept the above licence agreement ([Y,y]/[N,n])? y
*********************************************************************************
                     Welcome to install GBase products
*********************************************************************************
Environmental Checking on gcluster nodes.
CoordinateHost:
192.168.142.11
DataHost:
192.168.142.11
Are you sure to install GCluster on these nodes ([Y,y]/[N,n])? y
192.168.142.11       	Start install on host 192.168.142.11
192.168.142.10       	Start install on host 192.168.142.10
192.168.142.11       	mkdir /opt_prepare on host 192.168.142.11.
192.168.142.10       	mkdir /opt_prepare on host 192.168.142.10.
192.168.142.11       	Copying InstallTar.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying InstallTar.py to host 192.168.142.10:/opt_prepare
192.168.142.11       	Copying InstallFuns.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying rmt.py to host 192.168.142.10:/opt_prepare
192.168.142.11       	Copying SSHThread.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying SSHThread.py to host 192.168.142.10:/opt_prepare
192.168.142.11       	Copying RestoreLocal.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying RestoreLocal.py to host 192.168.142.10:/opt_prepare
192.168.142.11       	Copying pexpect.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying pexpect.py to host 192.168.142.10:/opt_prepare
192.168.142.11       	Copying bundle.tar.bz2 to host 192.168.142.11:/opt_prepare
192.168.142.10       	Updating corosync configure files.
192.168.142.11       	Copying bundle.tar.bz2 to host 192.168.142.11:/opt_prepare
192.168.142.10       	Updating corosync configure files.
192.168.142.11       	Copying bundle_data.tar.bz2 to host 192.168.142.11:/opt_prepare
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Installing gcluster.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
Update and sync configuration file...
Starting all gcluster nodes...
Sync coordinator system tables...
check database password ...
check database password successful
check rsync command status
use rsync command sync metadata
Adding new datanodes to gcware...
ExtendCluster Successfully

6、查看集群当前状态

[gbase@localhost gcinstall]$ gcadmin 
CLUSTER STATE:  ACTIVE
CLUSTER MODE:   NORMAL

=====================================================================
|               GBASE COORDINATOR CLUSTER INFORMATION               |
=====================================================================
|   NodeName   |       IpAddress       |gcware |gcluster |DataState |
---------------------------------------------------------------------
| coordinator1 |    192.168.142.10     | OPEN  |  OPEN   |    0     |
---------------------------------------------------------------------
| coordinator2 |    192.168.142.11     | OPEN  |  OPEN   |    0     |
---------------------------------------------------------------------
=================================================================
|                GBASE DATA CLUSTER INFORMATION                 |
=================================================================
|NodeName |       IpAddress       |gnode |syncserver |DataState |
-----------------------------------------------------------------
|  node1  |    192.168.142.10     | OPEN |   OPEN    |    0     |
-----------------------------------------------------------------
|  node2  |    192.168.142.11     | OPEN |   OPEN    |    0     |
-----------------------------------------------------------------
[gbase@localhost gcinstall]$ gcadmin showdistribution

              Distribution ID: 1 | State: new | Total segment num: 1

     Primary Segment Node IP                           Segment ID         Duplicate Segment node IP
========================================================================================================================
|    192.168.142.10                              |       1          |                                                  |
========================================================================================================================

我们可以看到管理节点已经添加成功，数据节点还没有添加分布策略，原来的分布策略ID为1。

7、配置新的分布策略

[gbase@localhost gcinstall]$ cat gcChangeInfo.xml 
<?xml version="1.0" encoding="utf-8"?>
<servers>
 <rack>
  <node ip="192.168.142.11"/>
  <node ip="192.168.142.10"/>
 </rack>
</servers>

[gbase@localhost gcinstall]$  gcadmin distribution gcChangeInfo.xml p 1 d 0
gcadmin generate distribution ...

[warning]: parameter [d num] is 0, the new distribution will has no segment backup
please ensure this is ok, input y or n: y
NOTE: node [192.168.142.11] is coordinator node, it shall be data node too
copy system table from 192.168.142.10 to 192.168.142.11
source ip: 192.168.142.10
target ip: 192.168.142.11
gcadmin generate distribution successful

[gbase@localhost gcinstall]$ gcadmin showdistribution

              Distribution ID: 2 | State: new | Total segment num: 2

     Primary Segment Node IP                           Segment ID         Duplicate Segment node IP
========================================================================================================================
|    192.168.142.11                              |       1          |                                                  |
------------------------------------------------------------------------------------------------------------------------
|    192.168.142.10                              |       2          |                                                  |
========================================================================================================================

              Distribution ID: 1 | State: old | Total segment num: 1

     Primary Segment Node IP                           Segment ID         Duplicate Segment node IP
========================================================================================================================
|    192.168.142.10                              |       1          |                                                  |
========================================================================================================================

我们可以看到现在有两个分布策略，后续我们删除老的分布策略。

8、初始化

[gbase@localhost gcinstall]$ gccli

GBase client 8.6.2.43-R33.132743. Copyright (c) 2004-2022, GBase.  All Rights Reserved.

gbase> initnodedatamap;
Query OK, 0 rows affected, 1 warning (Elapsed: 00:00:00.76)

9、关闭并行度

如果有需要调整优先级，做此操作。

gbase> set global gcluster_rebalancing_concurrent_count = 0;
Query OK, 0 rows affected, 1 warning (Elapsed: 00:00:00.01)

10、重分布

重分布支持instance, database、table三种等级。

gbase> rebalance instance;
Query OK, 1 row affected (Elapsed: 00:00:00.25)

11、调整优先级

根据现场实际情况来调整，也可以不调整。

（1）查看重分布状态
gbase> select * from  gclusterdb.rebalancing_status;
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
| index_name | db_name | table_name | tmptable | start_time                 | end_time | status   | percentage | priority | host | distribution_id |
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
| czg.czg    | czg     | czg        | NULL     | 2022-08-12 10:04:58.762000 | NULL     | STARTING |          0 |        5 | NULL |               2 |
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
1 row in set (Elapsed: 00:00:00.01)
（2）调整优先度

priority值小的，优先级高，改完之后，需加大并行度。

gbase> update gclusterdb.rebalancing_status set priority = 3 where index_name like 'czg.czg';
Query OK, 1 row affected (Elapsed: 00:00:00.18)
Rows matched: 1  Changed: 1  Warnings: 0

gbase> select * from  gclusterdb.rebalancing_status;
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
| index_name | db_name | table_name | tmptable | start_time                 | end_time | status   | percentage | priority | host | distribution_id |
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
| czg.czg    | czg     | czg        | NULL     | 2022-08-12 10:04:58.762000 | NULL     | STARTING |          0 |        3 | NULL |               2 |
+------------+---------+------------+----------+----------------------------+----------+----------+------------+----------+------+-----------------+
1 row in set (Elapsed: 00:00:00.01)

gbase> set global gcluster_rebalancing_concurrent_count = 5;
Query OK, 0 rows affected, 1 warning (Elapsed: 00:00:00.00)

12、查看重分布完成度

gbase> select * from  gclusterdb.rebalancing_status;
+------------+---------+------------+----------+----------------------------+----------------------------+-----------+------------+----------+-----------------------+-----------------+
| index_name | db_name | table_name | tmptable | start_time                 | end_time                   | status    | percentage | priority | host                  | distribution_id |
+------------+---------+------------+----------+----------------------------+----------------------------+-----------+------------+----------+-----------------------+-----------------+
| czg.czg    | czg     | czg        |          | 2022-08-12 10:33:59.337000 | 2022-08-12 10:33:59.654000 | COMPLETED |        100 |        3 | ::ffff:192.168.142.10 |               2 |
+------------+---------+------------+----------+----------------------------+----------------------------+-----------+------------+----------+-----------------------+-----------------+
1 row in set (Elapsed: 00:00:00.01)

13、查看是否有表使用老的策略

gbase> select * from gbase.table_distribution where data_distribution_id=1;
Empty set (Elapsed: 00:00:00.01)

如果有的话，请使用rebalance table 库名.表名，重新分布表。

14、删除老的刷新节点数据地图

gbase> refreshnodedatamap drop 1;
Query OK, 0 rows affected, 1 warning (Elapsed: 00:00:01.00)

15、删除老的分布策略

[gbase@localhost gcinstall]$ gcadmin rmdistribution 1
cluster distribution ID [1]
it will be removed now
please ensure this is ok, input y or n: y
gcadmin remove distribution [1] success

16、查看最终结果

各节点状态正常，分布策略是最新的，说明我们扩容成功啦。

[gbase@localhost gcinstall]$ gcadmin
CLUSTER STATE:  ACTIVE
CLUSTER MODE:   NORMAL

=====================================================================
|               GBASE COORDINATOR CLUSTER INFORMATION               |
=====================================================================
|   NodeName   |       IpAddress       |gcware |gcluster |DataState |
---------------------------------------------------------------------
| coordinator1 |    192.168.142.10     | OPEN  |  OPEN   |    0     |
---------------------------------------------------------------------
| coordinator2 |    192.168.142.11     | OPEN  |  OPEN   |    0     |
---------------------------------------------------------------------
=================================================================
|                GBASE DATA CLUSTER INFORMATION                 |
=================================================================
|NodeName |       IpAddress       |gnode |syncserver |DataState |
-----------------------------------------------------------------
|  node1  |    192.168.142.10     | OPEN |   OPEN    |    0     |
-----------------------------------------------------------------
|  node2  |    192.168.142.11     | OPEN |   OPEN    |    0     |
-----------------------------------------------------------------

[gbase@localhost gcinstall]$ gcadmin showdistribution

              Distribution ID: 2 | State: new | Total segment num: 2

     Primary Segment Node IP                           Segment ID         Duplicate Segment node IP
========================================================================================================================
|    192.168.142.11                              |       1          |                                                  |
------------------------------------------------------------------------------------------------------------------------
|    192.168.142.10                              |       2          |                                                  |
========================================================================================================================

三、踩坑点-db_root_pwd is not input, connect gncli failed

1、问题描述

重分布时，由于root密码不为空，所导致的问题。

[gbase@xdw0 gcinstall]$  gcadmin distribution gcChangeInfo.xml p 1 d 1
gcadmin generate distribution ...


db_root_pwd is not input, connect gncli failed
please input db_root_pwd and check gbased is running
gcadmin generate distribution failed

2、解决方法

添加参数：db_root_pwd

[gbase@xdw0 gcinstall]$  gcadmin distribution gcChangeInfo.xml p 1 d 1 db_root_pwd 'qwer1234'
gcadmin generate distribution ...

copy system table from 192.168.142.10 to 192.168.142.12
source ip: 192.168.142.10
target ip: 192.168.142.12
gcadmin generate distribution successful

四、踩坑点-HA event monitor thread call gcClmClusterTrack function fail（未解决）

之前我是两节点扩展到三节点，每个节点是3G，2个逻辑核，扩容出现的问题。

[root@localhost ~]# su - gbase
上一次登录：四 8月 11 17:29:07 CST 2022pts/6 上

[gbase@localhost gcinstall]$ ./gcinstall.py --silent=demo.options
*********************************************************************************
Thank you for choosing GBase product!


Please read carefully the following licencing agreement before installing GBase product:
TIANJIN GENERAL DATA TECHNOLOGY CO., LTD. LICENSE AGREEMENT
 
READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSETERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWAREMEDIA PACKAGE.  BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO THE TERMS OF THIS AGREEMENT.  IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS.  IF YOU DO NOT AGREE TO ALL THESE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND.
 

1.  CHINESE GOVERNMENT RESTRICTED.  If Software is being acquired by or on behalf of the Chinese Government , then the Government's rights in Software and accompanying documentation will be only as set forth in this Agreement.
 
2.  GOVERNING LAW.  Any action related to this Agreement will be governed by Chinese law: "COPYRIGHT LAW OF THE PEOPLE'S REPUBLIC OF CHINA","PATENT LAW OF THE PEOPLE'S REPUBLIC OF CHINA","TRADEMARK LAW OF THE PEOPLE'S REPUBLIC OF CHINA","COMPUTER SOFTWARE PROTECTION REGULATIONS OF THE PEOPLE'S REPUBLIC OF CHINA".  No choice of law rules of any jurisdiction will apply."
 

*********************************************************************************
Do you accept the above licence agreement ([Y,y]/[N,n])? y
*********************************************************************************
                     Welcome to install GBase products
*********************************************************************************
Environmental Checking on gcluster nodes.
CoordinateHost:
192.168.142.12
DataHost:
192.168.142.12
Are you sure to install GCluster on these nodes ([Y,y]/[N,n])? y
192.168.142.12       	Start install on host 192.168.142.12
192.168.142.11       	Start install on host 192.168.142.11
192.168.142.10       	Start install on host 192.168.142.10
192.168.142.12       	mkdir /opt_prepare on host 192.168.142.12.
192.168.142.11       	mkdir /opt_prepare on host 192.168.142.11.
192.168.142.10       	mkdir /opt_prepare on host 192.168.142.10.
192.168.142.12       	Copying InstallTar.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying InstallTar.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying InstallTar.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying InstallFuns.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying InstallFuns.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying InstallFuns.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying rmt.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying rmt.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying rmt.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying SSHThread.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying SSHThread.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying SSHThread.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying RestoreLocal.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying RestoreLocal.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying RestoreLocal.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying pexpect.py to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying pexpect.py to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying pexpect.py to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying BUILDINFO to host 192.168.142.12:/opt_prepare
192.168.142.11       	Copying BUILDINFO to host 192.168.142.11:/opt_prepare
192.168.142.10       	Copying BUILDINFO to host 192.168.142.10:/opt_prepare
192.168.142.12       	Copying bundle.tar.bz2 to host 192.168.142.12:/opt_prepare
192.168.142.11       	Updating corosync configure files.
192.168.142.10       	Updating corosync configure files.
192.168.142.12       	Copying bundle.tar.bz2 to host 192.168.142.12:/opt_prepare
192.168.142.11       	Updating corosync configure files.
192.168.142.10       	Updating corosync configure files.
192.168.142.12       	Copying bundle_data.tar.bz2 to host 192.168.142.12:/opt_prepare
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Installing gcluster.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Install gcluster on host 192.168.142.12 successfully.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
192.168.142.12       	Install gcluster on host 192.168.142.12 successfully.
192.168.142.11       	Install gcluster on host 192.168.142.11 successfully.
192.168.142.10       	Install gcluster on host 192.168.142.10 successfully.
Update and sync configuration file...
Starting all gcluster nodes...
Sync coordinator system tables...
check database password ...

这一直卡住，没有显示报错，看后台安装日志没有报错，在尝试登录数据库。

[root@localhost ~]# tail -f /opt/pkg/gcinstall/gcinstall.log 
2022-08-11 17:28:52,297-root-DEBUG rm -f /opt/pkg/gcinstall/corosync.conf192.168.142.12
2022-08-11 17:28:52,812-root-INFO sync corosync conf successfully.
2022-08-11 17:28:52,812-root-DEBUG Starting all gcluster nodes...
2022-08-11 17:28:59,753-root-INFO start service successfull on host 192.168.142.12.
2022-08-11 17:29:08,441-root-INFO start service successfull on host 192.168.142.10.
2022-08-11 17:29:10,182-root-INFO start service successfull on host 192.168.142.11.
2022-08-11 17:29:10,686-root-DEBUG /bin/chown -R gbase:gbase gcChangeInfo.xml
2022-08-11 17:29:10,730-root-DEBUG Sync coordinator system tables...
2022-08-11 17:29:10,730-root-INFO check database password ...
2022-08-11 17:29:10,730-root-INFO gccli -uroot -p'***' -e'use gbase'

查看/opt/gcluster/log/gcluster/express.log 日志，提示调用gcClmClusterTrack函数错误。

[root@localhost ~]# tail -f /opt/gcluster/log/gcluster/express.log 
2022-08-11 17:51:43.319 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:44.322 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:45.325 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:46.330 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:47.333 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:48.335 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:49.339 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:50.341 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail

2022-08-11 17:51:51.346 [ERROR] <HAEventHandler::HaEventMonitorThreadProc>: HA event monitor thread call gcClmClusterTrack function fail
阳光九叶草LXGZXJ
关注
  • 2
    点赞
  • 踩
  • 2
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
GBase 8a通过扩容的方式达到节点替换的目的
jingjing1068的博客
01-18 2145
GBase 8a支持节点替换，当某些服务器出现不可恢复的故障时，比如磁盘损坏，可以在修复后替换，或者用新节点做节点替换。在V8版本里，默认节点替换必须用老的IP，在V95版本的多VC模式，支持了集群空闲的备用节点freenode节点替换模式。本文介绍一种通过扩容的方式，采用新节点做数据计算节点替换的方案。 该场景一般发生在，故障节点不确认何时修好，而新服务又不允许更换IP的情况。 本方案只涉及计算数据节点，不涉及管理和调度节点。如需要替换的是这2种，请按照标准【节点替换】流程操作。 本文只针对不支持用新IP
南大数据库-gbase
01-14
南大数据库驱动连接jar包，gbase连接必不可少的jar包，放置于lib下，虽然南大数据库用的mysql的核心，并不是很好用，但是特定情况还是少不了它
GBase 8a 集群节点管理-扩容（多VC模式）
weixin_34421618的博客
03-23 940
GBase 8a 集群节点管理-扩容（多VC模式）
GBase 8a 集群节点管理-扩容（单VC模式）
weixin_34421618的博客
03-23 430
GBase 8a 集群节点管理-扩容（单VC模式）
GBase 8a 数据库集群扩容操作详细实例
老紫竹的专栏
09-18 1397
GBase 8a数据库集群，支持从现有集群扩容操作，可以同时扩容多个数据节点和管理节点。扩容一般是因为空间占用或者性能问题导致。GBase 通过重分布功能将数据重新分散到所有的数据节点上，以实现数据空间的再平衡。本文是一个详细操作步骤和手顺。 原文：http://www.gbase8.cn/1133 扩容和缩容是2个完全相反的结果，但大体操作步骤基本类似，只是相反的。缩容步骤请参考。GBase 8a 缩容操作步骤实例 目标 本文的目标，是将一个2节点的集群，扩容到3个节点，也就是增加1个管理和数据.
GBASE 8s 分布式功能之在线扩容
因为吃过天津一家超好吃的八珍豆腐从而改名为八珍豆腐的博客
05-23 295
GBase 8s分布式架构通过分片规则多版本方式实现在线扩容缩容。扩容过程如下： 分片规则变更后保存历史版本； GCWare向GCluster同时返回全部版本的分片信息； 提供分片刷新工具，遍历历史分片规则，在所有HG上按表逐行将数据从历史分片迁移到新分片； 当历史分片数据全部迁移到新分片后（无法通过旧分片规则在HG上查询到数据），删除历史分片规则； 分片刷新工具对业务无影响，可随意中断，随时继续； 扩容服务器可立刻提供服务； 缩容服务器需要等待分片刷新工具将数据迁移完成后才能移除服务器。..
南大通用Gbase-jdbc-drvier驱动
10-31
Gbase-jdbc-driver是由南大通用数据技术股份有限公司开发的一款数据库连接驱动，主要用于Java应用程序与Gbase 8系列数据库之间的通信。Gbase 8是南大通用推出的一种高性能、高可用性的分布式列式数据库系统，广泛...
南大通用jdbc连接驱动gbase-connector-java-8.3.81.51
10-14
南大通用jdbc连接驱动，gbase-connector-java-8.3.81.51,版本还是比较新的，可以下载来使用，如果有何问题，可留言。
南大通用数据库(GBase 8s) , gbasedbtjdbc-3.3.0-2-36477d.jar
最新发布
05-17
南大通用数据库jar包，gbasedbtjdbc_3.3.0_2_36477d.jar
gbase-connector-java-8.3.81.51_build50.0-bin.jar
08-14
南大通用Gbase数据库jdbc连接驱动gbase-connector-java-8.3.81.51_build50.0-bin.jar
GBase 8a -扩容缩容优化
Mr_dar的博客
12-23 371
多节点集群缩容时，由于内存不足导致缩容失败。正确进行参数配置，可避免缩容时由于配置问题而导致的内存不足报错。 1. gnode 配置参数在缩容情况下： 最高值： MAX_PARALLEL_DEGREE = （ PROCESS_COUNT > ((TOTAL_NODES_COUNT-1) // (NEW_NODE_COUNT)) ? PROCESS_COUNT / ((TOTAL_NODES_COUNT-1) // (NEW_NODE_COUNT)) : 1）; RESULT_BUFF_COU.
南大通用数据库-Gbase-8a-学习-07-集群节点缩容（8.6版本）
qq_45111959的博客
08-12 538
如果大家只缩容数据节点，在二、13中只写dataHost，不写coordinateHost ，其他的内容和上面的例子不变。existCoordinateHost写要保留的管理节点ip，如果有的话，进行rebalance table 库名.表名。coordinateHost 写要卸载的管理节点ip，existDataHost写要保留的数据节点ip。我们只留保留节点的信息，缩容节点的信息进行剔除。dataHost 写要卸载的数据节点ip，里面存放已经缩容完的数据节点信息。只剩下一个节点，缩容成功。.......
GBase8a节点及服务部署方案
CornerHebut的博客
05-27 392
方案1 coordinator节点与data节点分别部署在不同服务器上： 管理集群的节点单独部署在管理服务器上，所有coordinator节点需在一个网段内。 数据集群的节点独立部署在数据服务器上，data节点可跨网段部署，只要保证网络通信质量即可。 方案2 coordinator节点和data节点共同部署在同一个服务器上： 管理集群节点和数据集群的节点部署在同一个服务器上。 根据集群规模和业务并发量，Coordinator节点个数建议3~11的奇数个，如小规模集群（data节点数<=10）设
ceph集群的扩展（centos7环境）
CloudXli的博客
03-13 2266
首先可以看看我原来搭建的三节点ceph环境： http://blog.csdn.net/cloudxli/article/details/78651866 后来在原来的mon节点上安装了mds（还是三个节点）变成下面： http://blog.csdn.net/cloudxli/article/details/79265120 现在我要做的是在原来的基础上添加一个节点变成下面的这个集群...
Centos7下FastDFS 集群配置及添加storage节点+nginx
xiaoweiqb的博客
03-29 8579
配置最终目标 以4台服务做集群，其中2台作为tracker服务器又作为storage节点，tracker以先启动为leader，后启动为client，这个可以互换，另外两台作为纯storage节点，并分配两个group为group1与group2以下服务器说明： 192.168.10.152 tracker leader   group1，storage1 192.168.10.153 tr
GBase 8a 集群节点管理-缩容
weixin_34421618的博客
03-24 345
GBase 8a 集群节点管理-缩容
GBase 8a 集群gcadmin各种报错排查
老紫竹的专栏
09-28 1950
本文价绍GBase 8a数据库集群的管理命令报错的各种情况，针对corosync、gcware服务。 本文会随着使用不断更新，最新文章请参考GBase 8a 集群故障自助查询-gcadmin类 各种日志，请参考 GBase 8a集群日志所在目录位置 确认服务是否启动 V8 ps -ef|grep corosync v9 ps -ef|grep gcware 如果服务不存在，且确实没有启动服务，那么请先启动。如果启动了，还是报错或进程不再，请根据后面报错信息排查。 ...
GBase 8a V95安装时报错Dir dbaUser ‘gbase’ doesn’t have write and privilege to this dirctory
Mr_dar的博客
03-25 450
GBase 8a V95版本在安装时，对安装目录必须有写入权限。新版本自动检测了该目录，如果无写入权限，将报这个错判。解决方案就是该目录有dbaUser的写入权限。 报错样例 Dir '/opt',dbaUser 'gbase' doesn't have write and privilege to this dirctory '/opt' 原因 安装配置文件里的安装目录， 没有dbaUser, 一般是gbase，的写入权限。 解决方案 将所有安装节点的安装目录，增加dbaUser的写入权限
Eclipse内存溢出的解决办法
bobo_93的博客
05-25 2868
在Eclipse根目录下找到eclipse.ini文件，打开并修改如下： -showsplash org.eclipse.platform --launcher.XXMaxPermSize 512m -vmargs -Xms256m -Xmx512m -XX:PermSize=128M -XX:MaxPermSize=128M -vmargs这个参数是对虚拟机的
GBase 8a集群SQL参考手册-南大通用数据技术有限公司
"GBase 8a Cluster SQL参考手册提供了南大通用数据技术有限公司的GBase 8a集群数据库系统的SQL语法和数据类型的详细信息。该手册强调了文档的版权和使用规定，用户只能在合法范围内查阅、复制和打印。GBase是南大...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值