当前位置: 首页 > article >正文

云贝教育 |【技术文章】OpenTenBase_V2.6基于麒麟V10源码编译安装

本文为云贝教育 刘老师 原创,请尊重知识产权,转发请注明出处,不接受任何抄袭、演绎和未经注明出处的转载。

前言:什么是OpenTenBase 

OpenTenBase 是一个提供写可靠性,多主节点数据同步的关系数据库集群平台。你可以将 OpenTenBase 配置一台或者多台主机上, OpenTenBase 数据存储在多台物理主机上面。数据表的存储有两种方式, 分别是 distributed 或者 replicated ,当向OpenTenBase发送查询 SQL时, OpenTenBase 会自动向数据节点发出查询语句并获取最终结果。

OpenTenBase 采用分布式集群架构(如下图), 该架构分布式为无共享(share nothing)模式,节点之间相应独立,各自处理自己的数据,处理后的结果可能向上层汇总或在节点间流转,各处理单元之间通过网络协议进行通信,并行处理和扩展能力更好,这也意味着只需要简单的x86服务器就可以部署 OpenTenBase 数据库集群

下面简单解读一下OpenTenBase的三大模块

  • Coordinator:协调节点(简称CN)

业务访问入口,负责数据的分发和查询规划,多个节点位置对等,每个节点都提供相同的数据库视图;在功能上CN上只存储系统的全局元数据,并不存储实际的业务数据。

  • Datanode:数据节点(简称DN)

每个节点还存储业务数据的分片在功能上,DN节点负责完成执行协调节点分发的执行请求。

  • GTM:全局事务管理器(Global Transaction Manager)

负责管理集群事务信息,同时管理集群的全局对象,比如序列等。

本文将详细介绍如何从源码开始,完成 OpenTenBase V2.6 的编译和安装过程。

一、安装准备及规划

1.1 环境要求

在开始编译之前,请确保你的系统满足以下要求:

  • 操作系统:TencentOS 2, TencentOS 3, OpenCloudOS, CentOS 7, CentOS 8, Ubuntu
  • 内存:至少 4GB RAM
  • 磁盘空间:至少10GB,足够的磁盘空间用于源码下载、编译和安装

1.2 软件环境

软件名称

软件版本
麒麟服务端操作系统kylin_v10
OpenTenBase V2.6


1.3 集群规划

  • 集群规划

下面以两台服务器上搭建1GTM主,1GTM备,2CN主(CN主之间对等,因此无需备CN),2DN主,2DN备的集群,该集群为具备容灾能力的最小配置

机器1:192.168.2.136
机器2:192.168.2.137

集群规划如下:

节点名称

IP数据目录

GTM master

192.168.2.136

/data/opentenbase/data/gtm

GTM slave

192.168.2.137

/data/opentenbase/data/gtm

CN1

192.168.2.136

/data/opentenbase/data/coord

CN2

192.168.2.137

/data/opentenbase/data/coord

DN1 master

192.168.2.136

/data/opentenbase/data/dn001

DN1 slave

192.168.2.137

/data/opentenbase/data/dn001

DN2 master

192.168.2.137

/data/opentenbase/data/dn002

DN2 slave

192.168.2.136

/data/opentenbase/data/dn002

二. 安装依赖

根据你的操作系统,使用以下命令安装必要的依赖包:

对于基于 Red Hat 的系统(如 CentOS):

dnf -y install gcc make readline-devel zlib-devel openssl-devel uuid-devel bison flex git

对于基于 Debian 的系统(如 Ubuntu):

sudo apt-get update
sudo apt-get -y install gcc make libreadline-dev zlib1g-dev libssl-dev libossp-uuid-dev bison flex git

  

三. 创建 OpenTenBase 用户

所有需要安装 OpenTenBase 集群的机器上都需要创建 opentenbase 用户,并设置相应的目录权限。

#创建 opentenbase 用户
useradd -d /data/opentenbase -s /bin/bash -m opentenbase  

#设置密码
passwd opentenbase
--mko0-pl,

四. 获取安装包

4.1 git获取源码

  • 创建软件目录
[root]
mkdir /dbsoft
  • 使用 git 克隆 OpenTenBase 的源码仓库:

克隆源码(root用户)

git clone https://github.com/OpenTenBase/OpenTenBase

4.2 下载源码包

登录git,下载最新的v2.6.0版本

https://github.com/OpenTenBase/OpenTenBase/tags

五. 编译源码

5.1 配置安装环境变量

所有节点都要操作

mkdir -p /data/opentenbase/{install,dbsoft}
chown -R opentenbase:opentenbase /data/opentenbase

5.2 编绎安装

  • 将源码包移动到源码目录
#复制安装包
cp /dbsoft/OpenTenBase-2.6.0.tar.gz /data/opentenbase/dbsoft

#解压
tar -zxvf OpenTenBase-2.6.0.tar.gz 
  • 进入源码目录并进行编译:
#进入源码目录
/data/opentenbase/dbsoft/OpenTenBase-2.6.0

#赋予配置脚本执行权限
chmod +x configure*  

#配置编译选项
./configure --prefix=/data/opentenbase/install/opentenbase_bin_v2.6 --enable-user-switch --with-openssl --with-ossp-uuid CFLAGS=-g  

#编译安装软件
make clean  
make -sj  4
make install  

#编译 contrib 目录下的工具
cd contrib
make -sj 4
make install

六、集群初始化

6.1 禁用 SELinux 和 防火墙 (可选)

--关闭selinux
vi /etc/selinux/config 
# disable SELinux, change SELINUX=enforcing to SELINUX=disabled

--关闭防火墙
systemctl disable firewalld
systemctl stop firewalld

6.2. 配置 SSH 

互信为了方便后续操作,建议配置opentenbase机器间的 SSH 互信:

[opentenbase]
#切换opentenbase用户
su - opentenbase

# 192.168.2.136生成 SSH 密钥对
ssh-keygen -t rsa  

# 将公钥复制到其他节点
ssh-copy-id -i ~/.ssh/id_rsa.pub opentenbase@192.168.2.136
ssh-copy-id -i ~/.ssh/id_rsa.pub opentenbase@192.168.2.137
ssh-copy-id -i ~/.ssh/id_rsa.pub opentenbase@192.168.2.138

6.3. 配置opentenbase环境变量

集群所有机器都需要配置

[opentenbase]
$ vim ~/.bashrc
export OPENTENBASE_HOME=/data/opentenbase/install/opentenbase_bin_v2.6
export PATH=$OPENTENBASE_HOME/bin:$PATH
export LD_LIBRARY_PATH=$OPENTENBASE_HOME/lib:${LD_LIBRARY_PATH}
export LC_ALL=C

6.4. 配置root环境变量

集群所有机器都需要配置,把opentenbase用户的$PATH环境变量添加到 /etc/environment

[root]
cat /etc/environment
PATH=/data/opentenbase/install/opentenbase_bin_v2.6/bin:/data/opentenbase/.local/bin:/data/opentenbase/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin

6.5. 初始化pgxc_ctl.conf文件

[opentenbase]
mkdir /data/opentenbase/pgxc_ctl
cd /data/opentenbase/pgxc_ctl
vim pgxc_ctl.conf

如下,是结合上文描述的IP,端口,数据库目录,二进制目录等规划来写的pgxc_ctl.conf文件。

pgxc_ctl.conf配置如下:

#!/bin/bash
# Double Node Config

#主要调整IP地址即可
IP_1=192.168.2.136
IP_2=192.168.2.137

pgxcInstallDir=/data/opentenbase/install/opentenbase_bin_v2.6
pgxcOwner=opentenbase
defaultDatabase=postgres
pgxcUser=$pgxcOwner
tmpDir=/tmp
localTmpDir=$tmpDir
configBackup=n
configBackupHost=pgxc-linker
configBackupDir=$HOME/pgxc
configBackupFile=pgxc_ctl.bak


#---- GTM ----------
gtmName=gtm
gtmMasterServer=$IP_1
gtmMasterPort=50001
gtmMasterDir=/data/opentenbase/data/gtm
gtmExtraConfig=none
gtmMasterSpecificExtraConfig=none
gtmSlave=y
gtmSlaveServer=$IP_2
gtmSlavePort=50001
gtmSlaveDir=/data/opentenbase/data/gtm
gtmSlaveSpecificExtraConfig=none

#---- Coordinators -------
coordMasterDir=/data/opentenbase/data/coord
coordArchLogDir=/data/opentenbase/data/coord_archlog

coordNames=(cn001 cn002 )
coordPorts=(30004 30004 )
poolerPorts=(31110 31110 )
coordPgHbaEntries=(0.0.0.0/0)
coordMasterServers=($IP_1 $IP_2)
coordMasterDirs=($coordMasterDir $coordMasterDir)
coordMaxWALsernder=2
coordMaxWALSenders=($coordMaxWALsernder $coordMaxWALsernder )
coordSlave=n
coordSlaveSync=n
coordArchLogDirs=($coordArchLogDir $coordArchLogDir)

coordExtraConfig=coordExtraConfig
cat > $coordExtraConfig <<EOF
#================================================
# Added to all the coordinator postgresql.conf
# Original: $coordExtraConfig

include_if_exists = '/data/opentenbase/global/global_opentenbase.conf'

wal_level = replica
wal_keep_segments = 256 
max_wal_senders = 4
archive_mode = on 
archive_timeout = 1800 
archive_command = 'echo 0' 
log_truncate_on_rotation = on 
log_filename = 'postgresql-%M.log' 
log_rotation_age = 4h 
log_rotation_size = 100MB
hot_standby = on 
wal_sender_timeout = 30min 
wal_receiver_timeout = 30min 
shared_buffers = 1024MB 
max_pool_size = 2000
log_statement = 'ddl'
log_destination = 'csvlog'
logging_collector = on
log_directory = 'pg_log'
listen_addresses = '*'
max_connections = 2000

EOF

coordSpecificExtraConfig=(none none)
coordExtraPgHba=coordExtraPgHba
cat > $coordExtraPgHba <<EOF

local   all             all                                     trust
host    all             all             0.0.0.0/0               trust
host    replication     all             0.0.0.0/0               trust
host    all             all             ::1/128                 trust
host    replication     all             ::1/128                 trust


EOF


coordSpecificExtraPgHba=(none none)
coordAdditionalSlaves=n 
cad1_Sync=n

#---- Datanodes ---------------------
dn1MstrDir=/data/opentenbase/data/dn001
dn2MstrDir=/data/opentenbase/data/dn002
dn1SlvDir=/data/opentenbase/data/dn001
dn2SlvDir=/data/opentenbase/data/dn002
dn1ALDir=/data/opentenbase/data/datanode_archlog
dn2ALDir=/data/opentenbase/data/datanode_archlog

primaryDatanode=dn001
datanodeNames=(dn001 dn002)
datanodePorts=(40004 40004)
datanodePoolerPorts=(41110 41110)
datanodePgHbaEntries=(0.0.0.0/0)
datanodeMasterServers=($IP_1 $IP_2)
datanodeMasterDirs=($dn1MstrDir $dn2MstrDir)
dnWALSndr=4
datanodeMaxWALSenders=($dnWALSndr $dnWALSndr)

datanodeSlave=y
datanodeSlaveServers=($IP_2 $IP_1)
datanodeSlavePorts=(50004 54004)
datanodeSlavePoolerPorts=(51110 51110)
datanodeSlaveSync=n
datanodeSlaveDirs=($dn1SlvDir $dn2SlvDir)
datanodeArchLogDirs=($dn1ALDir/dn001 $dn2ALDir/dn002)

datanodeExtraConfig=datanodeExtraConfig
cat > $datanodeExtraConfig <<EOF
#================================================
# Added to all the coordinator postgresql.conf
# Original: $datanodeExtraConfig

include_if_exists = '/data/opentenbase/global/global_opentenbase.conf'
listen_addresses = '*' 
wal_level = replica 
wal_keep_segments = 256 
max_wal_senders = 4
archive_mode = on 
archive_timeout = 1800 
archive_command = 'echo 0' 
log_directory = 'pg_log' 
logging_collector = on 
log_truncate_on_rotation = on 
log_filename = 'postgresql-%M.log' 
log_rotation_age = 4h 
log_rotation_size = 100MB
hot_standby = on 
wal_sender_timeout = 30min 
wal_receiver_timeout = 30min 
shared_buffers = 1024MB 
max_connections = 4000 
max_pool_size = 4000
log_statement = 'ddl'
log_destination = 'csvlog'
wal_buffers = 1GB

EOF

datanodeSpecificExtraConfig=(none none)
datanodeExtraPgHba=datanodeExtraPgHba
cat > $datanodeExtraPgHba <<EOF

local   all             all                                     trust
host    all             all             0.0.0.0/0               trust
host    replication     all             0.0.0.0/0               trust
host    all             all             ::1/128                 trust
host    replication     all             ::1/128                 trust


EOF


datanodeSpecificExtraPgHba=(none none)

datanodeAdditionalSlaves=n
walArchive=n

6.6. 分发二进制包

在一个节点上配置好配置文件后,使用 pgxc_ctl 工具将二进制包部署到所有节点:

[opentenbase@db1 pgxc_ctl]$ pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 
/usr/bin/bash
Installing pgxc_ctl_bash script as /home/opentenbase/pgxc_ctl/pgxc_ctl_bash.
Installing pgxc_ctl_bash script as /home/opentenbase/pgxc_ctl/pgxc_ctl_bash.
Reading configuration using /home/opentenbase/pgxc_ctl/pgxc_ctl_bash --home /home/opentenbase/pgxc_ctl --configuration /data/opentenbase/pgxc_ctl/pgxc_ctl.conf
Finished reading configuration.
   ******** PGXC_CTL START ***************

Current directory: /home/opentenbase/pgxc_ctl
PGXC 【这里输入指令】 deploy all

分发日志

Deploying Postgres-XL components to all the target servers.
Prepare tarball to deploy ... 
Deploying to the server 192.168.2.136.
Deploying to the server 192.168.2.137.
Deployment done.

6.7. 初始化集群

使用 pgxc_ctl 工具初始化集群:

 pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 
# 初始化集群
pgxc_ctl init all

初始化日志


。。。省略
2024-10-10 03:53:35.680 GMT [64489,coord(0.0)] LOG:  skipping missing configuration file "/data/opentenbase/global/global_opentenbase.conf"
2024-10-10 03:53:35.680 GMT [64489,coord(0.0)] LOG:  skipping missing configuration file "/data/opentenbase/global/global_opentenbase.conf"
2024-10-10 11:53:35.682 CST [64489,coord(0.0)] LOG:  listening on IPv4 address "0.0.0.0", port 50004
2024-10-10 11:53:35.682 CST [64489,coord(0.0)] LOG:  listening on IPv6 address "::", port 50004
2024-10-10 11:53:35.683 CST [64489,coord(0.0)] LOG:  listening on Unix socket "/tmp/.s.PGSQL.50004"
2024-10-10 11:53:44.803 CST [64489,coord(0.0)] LOG:  init committs shmem.
2024-10-10 11:53:50.550 CST [64489,coord(0.0)] LOG:  could not open file "global/pg_crypt_key.map":No such file or directory for bufFile merging.
2024-10-10 11:53:50.550 CST [64489,coord(0.0)] LOG:  start rel crypt load mapfile
2024-10-10 11:53:50.550 CST [64489,coord(0.0)] LOG:  could not open file "global/pg_rel_crypt.map":No such file or directory for bufFile merging.
2024-10-10 11:53:50.550 CST [64489,coord(0.0)] LOG:  end rel crypt load mapfile
2024-10-10 11:53:58.003 CST [64489,coord(0.0)] LOG:  redirecting log output to logging collector process
2024-10-10 11:53:58.003 CST [64489,coord(0.0)] HINT:  Future log output will appear in directory "pg_log".
2024-09-06 19:34:20.971 GMT [220835,coord(0.0)] LOG:  skipping missing configuration file "/data/opentenbase/global/global_opentenbase.conf"
2024-09-06 19:34:20.971 GMT [220835,coord(0.0)] LOG:  skipping missing configuration file "/data/opentenbase/global/global_opentenbase.conf"
2024-09-07 03:34:20.972 CST [220835,coord(0.0)] LOG:  listening on IPv4 address "0.0.0.0", port 54004
2024-09-07 03:34:20.973 CST [220835,coord(0.0)] LOG:  listening on IPv6 address "::", port 54004
2024-09-07 03:34:20.973 CST [220835,coord(0.0)] LOG:  listening on Unix socket "/tmp/.s.PGSQL.54004"
2024-09-07 03:34:20.974 CST [220835,coord(0.0)] FATAL:  could not map anonymous shared memory: Cannot allocate memory
2024-09-07 03:34:20.974 CST [220835,coord(0.0)] HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 5500862692 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.
2024-09-07 03:34:20.974 CST [220835,coord(0.0)] LOG:  database system is shut down
pg_ctl: could not start server
Examine the log output.

Done.
ALTER NODE cn001 WITH (HOST='192.168.2.136', PORT=30004);
ALTER NODE
CREATE NODE cn002 WITH (TYPE='coordinator', HOST='192.168.2.137', PORT=30004);
CREATE NODE
CREATE NODE dn001 WITH (TYPE='datanode', HOST='192.168.2.136', PORT=40004, PRIMARY, PREFERRED);
CREATE NODE
CREATE NODE dn002 WITH (TYPE='datanode', HOST='192.168.2.137', PORT=40004);
CREATE NODE
SELECT pgxc_pool_reload();
 pgxc_pool_reload 
------------------
 t
(1 row)

CREATE NODE cn001 WITH (TYPE='coordinator', HOST='192.168.2.136', PORT=30004);
CREATE NODE
ALTER NODE cn002 WITH (HOST='192.168.2.137', PORT=30004);
ALTER NODE
CREATE NODE dn001 WITH (TYPE='datanode', HOST='192.168.2.136', PORT=40004, PRIMARY);
CREATE NODE
CREATE NODE dn002 WITH (TYPE='datanode', HOST='192.168.2.137', PORT=40004, PREFERRED);
CREATE NODE
SELECT pgxc_pool_reload();
 pgxc_pool_reload 
------------------
 t
(1 row)

Done.
EXECUTE DIRECT ON (dn001) 'CREATE NODE cn001 WITH (TYPE=''coordinator'', HOST=''192.168.2.136'', PORT=30004)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn001) 'CREATE NODE cn002 WITH (TYPE=''coordinator'', HOST=''192.168.2.137'', PORT=30004)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn001) 'ALTER NODE dn001 WITH (TYPE=''datanode'', HOST=''192.168.2.136'', PORT=40004, PRIMARY, PREFERRED)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn001) 'CREATE NODE dn002 WITH (TYPE=''datanode'', HOST=''192.168.2.137'', PORT=40004, PREFERRED)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn001) 'SELECT pgxc_pool_reload()';
 pgxc_pool_reload 
------------------
 t
(1 row)

EXECUTE DIRECT ON (dn002) 'CREATE NODE cn001 WITH (TYPE=''coordinator'', HOST=''192.168.2.136'', PORT=30004)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn002) 'CREATE NODE cn002 WITH (TYPE=''coordinator'', HOST=''192.168.2.137'', PORT=30004)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn002) 'CREATE NODE dn001 WITH (TYPE=''datanode'', HOST=''192.168.2.136'', PORT=40004, PRIMARY, PREFERRED)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn002) 'ALTER NODE dn002 WITH (TYPE=''datanode'', HOST=''192.168.2.137'', PORT=40004, PREFERRED)';
EXECUTE DIRECT
EXECUTE DIRECT ON (dn002) 'SELECT pgxc_pool_reload()';
 pgxc_pool_reload 
------------------
 t
(1 row)

Done.

6.8. 查看集群状态

[opentenbase@db1 pgxc_ctl]$ pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 

# 启动集群
pgxc_ctl monitor all

 日志如下

Running: gtm master
Running: gtm slave
Running: coordinator master cn001
Running: coordinator master cn002
Running: datanode master dn001
Running: datanode slave dn001
Running: datanode master dn002
Not running: datanode slave dn002

 

6.9. 安装错误处理

1)日志查看

一般init集群出错,终端会打印出错误日志,通过查看错误原因,更改配置即可,或者可以通过/data/opentenbase/pgxc_ctl/pgxc_log路径下的错误日志查看错误,排查配置文件的错误

[opentenbase@db1 ~]$ cd ~/pgxc_ctl/pgxc_log/
[opentenbase@db1 pgxc_log]$ ll
total 1052
-rw-r--r-- 1 opentenbase opentenbase   2585 Sep  7 03:19 213564_pgxc_ctl.log
-rw-r--r-- 1 opentenbase opentenbase    767 Sep  7 03:20 213793_pgxc_ctl.log
-rw-r--r-- 1 opentenbase opentenbase    749 Sep  7 03:20 213805_pgxc_ctl.log
-rw-r--r-- 1 opentenbase opentenbase 477889 Sep  7 03:22 213813_pgxc_ctl.log
-rw-r--r-- 1 opentenbase opentenbase 584714 Sep  7 03:41 214355_pgxc_ctl.log

2)清理集群重新安装

通过运行 pgxc_ctl 工具,执行clean all命令删除已经初始化的文件,修改pgxc_ctl.conf文件,重新执行init all命令重新发起初始化。

[opentenbase@db1 pgxc_ctl]$ pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 

#PGXC clean all

3) 常见问题

  • 执行inti all时,提示pg_ctl命令找不到

这样的问题,通常是环境变量的问题,通过root用户配置/etc/environment 解决

[root]
$ cat /etc/environment 
PATH=/data/opentenbase/install/opentenbase_bin_v2.6/bin:/data/opentenbase/.local/bin:/data/opentenbase/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin
  • 执行inti all时,提示无法创建目录
mkdir: cannot create directory '/data/opentenbase': Permission denied

这样的问题,通常是分发节点上,没有创建对应的目录

解决方案:检查所有节点的目录配置,如果没有创建,创建即可。

mkdir -p /data/opentenbase/{install,dbsoft}
chown -R opentenbase:opentenbase /data/opentenbase

、集群访问

访问OpenTenBase集群和访问单机的PostgreSQL基本上无差别,我们可以通过任意一个CN访问数据库集群:例如通过连接CN节点select pgxc_node表即可查看集群的拓扑结构(当前的配置下备机不会展示在pgxc_node中),在Linux命令行下通过psql访问的具体示例如下

7.1 登录cn主节点

[opentenbase@db1 pgxc_log]$ psql -h 192.168.2.136 -p 30004 -d postgres -U opentenbase
psql (PostgreSQL 10.0 OpenTenBase V2)
Type "help" for help.

postgres=# 

 

7.2 使用数据库前需要创建default group以及sharding表

OpenTenBase使用datanode group来增加节点的管理灵活度,要求有一个default group才能使用,因此需要预先创建;一般情况下,会将节点的所有datanode节点加入到default group里 另外一方面,OpenTenBase的数据分布为了增加灵活度,加了中间逻辑层来维护数据记录到物理节点的映射,我们叫sharding,所以需要预先创建sharding,命令如下:

postgres=# create default node group default_group  with (dn001,dn002);
CREATE NODE GROUP
postgres=# create sharding group to group default_group;
CREATE SHARDING GROUP

 

7.3 创建数据库,用户,创建表,增删查改等操作

postgres=# create database test;
CREATE DATABASE
postgres=# create user test with password 'test';
CREATE ROLE
postgres=# alter database test owner to test;
ALTER DATABASE
postgres=# \c test test
You are now connected to database "test" as user "test".
test=> create table foo(id bigint, str text) distribute by shard(id);
CREATE TABLE
test=> insert into foo values(1, 'tencent'), (2, 'shenzhen');
COPY 2
test=> select * from foo;
 id |   str    
----+----------
  1 | tencent
  2 | shenzhen
(2 rows)

 

八、集群启停

8.1 停止集群

[opentenbase@db1 pgxc_ctl]$ pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 

PGXC stop all -m fast

停止日志

Stopping all the coordinator masters.
Stopping coordinator master cn001.
Stopping coordinator master cn002.

Done.
Stopping all the datanode slaves.
Stopping datanode slave dn001.
Stopping datanode slave dn002.

pg_ctl: PID file "/data/opentenbase/data/dn002/postmaster.pid" does not exist
Is server running?

Authorized users only. All activities may be monitored and reported.

Authorized users only. All activities may be monitored and reported.
Stopping all the datanode masters.
Stopping datanode master dn001.
Stopping datanode master dn002.

Done.
Stop GTM slave

waiting for server to shut down.... done
server stopped

Stop GTM master

waiting for server to shut down.... done
server stopped

 

8.2 启动集群

[opentenbase@db1 pgxc_ctl]$ pgxc_ctl -c /data/opentenbase/pgxc_ctl/pgxc_ctl.conf 

PGXC start all

 

九、结语

通过以上步骤,你已经成功地从源码编译并安装了 OpenTenBase V2.6。现在你可以开始使用 OpenTenBase 来管理你的分布式数据库集群。
 


http://www.kler.cn/news/355353.html

相关文章:

  • leetcode动态规划(六)-不同路径(有障碍物)
  • Java学习Day25:基础篇15:反射
  • MuSig2(一种多签名方案,具有签名聚合的特性
  • Python近红外光谱数据分析技术
  • IPv6 DNS简介
  • 一种用于机械手自适应抓取控制的紧凑型指尖形视触觉传感器
  • 【银行科技岗】相关考试知识点总结及部分考题
  • 学习的文档10/14
  • 系统共享库(Shared Library)
  • 重置时把el-tree树节点选中状态取消
  • Flink有状态计算
  • 【Golang】合理运用泛型,简化开发流程
  • ubuntu 使用appimage安装的应用,应该怎么创建桌面的快捷方式
  • 设定一个抽奖系统
  • Java高级Day54-正则表达式底层实现
  • Kerberos4简单复现
  • IP不纯净的后果及解决方案
  • 【JPCS独立出版,EI检索稳定】第三届能源互联网及电力系统国际学术会议(ICEIPS 2024)
  • React Componet类组件详解(老项目)
  • 数据结构编程实践20讲(Python版)—10B+树