How to deploy AntDB Community Version on a virtual machine on VMware Workstation—P2

Download at: http://www.antdb.net/download, choose X86 version under Open Euler

AntDB supports both centralized and distributed deployment methods, in practice, customers can flexibly choose the suitable deployment method according to their actual business situation.

In order to help you better complete the AntDB Community Version deployment, the AntDB database team has prepared a guidance document at:http://www.antdb.net/72_install,we can refer to the guidance document for AntDB Community Version deployment.

A.Centralized Deployment

Centralized deployment can be divided into centralized stand-alone deployment and centralized highly available cluster deployment, where stand-alone deployment is used for testing and single node use, and highly available cluster deployment is used for production environment to ensure high availability.

1.Centralized Stand-alone Deployment

Take 192.168.37.130 machine as an example, use CRT tool or xshell, etc., to login to the server.

1). Create a user
useradd -d /home/antdb -m antdb

2). Change the password
passwd antdb
Change the password of the user antdb
New password:
Retype the new password:
passwd: All authentication tokens have been successfully updated

3). Copy the installation package (antdb-ce-7.2.0.openeuler20.x86_64.tar.gz) to the directory of /home/antdb, and modify the permissions of the package.
chown -R antdb:antdb antdb-ce-7.2.0.openeuler20.x86_64.tar.gz

4). Switch to antdb user and unzip
su – antdb
tar xf antdb-ce-7.2.0.openeuler20.x86_64.tar.gz

5). Enter to the package directory and deploy the database
cd antdb-ce-7.2.0.openeuler20.x86_64

sh antdb_install.sh

The output steps are as follows:

At this point, the centralized standalone deployment of AntDB Community Version is completed. You can login to the database to operate, and the operation method is in line with the common operation habits of DBAs (database administrators), so if you have previous experience in using other transactional databases, you can easily get started.

2.Centralized High Available Cluster Deployment

1). Since the installation method is the same, the high available cluster deployment directly uses the software already installed on the standalone machine. Stop the deployed centralized standalone machine and keep the deployed software directory unchanged
pg_ctl stop -D /home/antdb/app/antdb/data/

2). Configure ssh-free between servers, configure sudo privileges for antdb users
ssh-keygen -t rsa
ssh-copy-id 192.168.37.130
ssh-copy-id 192.168.37.131
ssh-copy-id 192.168.37.132

visudo (operate on 3 machines)

3). Turn off the firewall, selinux (operate on 3 machines)
systemctl stop firewalld.service
systemctl status firewalld.service

vi /etc/selinux/config (Modifying selinux requires a reboot of the host, operate on 3 machines)

Temporary shutdown can be done with setenforce 0

4). Edit the high available deployment configuration file
cd /home/antdb/antdb-ce-7.2.0.openeuler20.x86_64/setup/common


vi initconf-c.ini
## clusterinfo configuration item description:
##
## cluster_type Classification:
## C_ALONE indicates a centralized standalone version: only clusterinfo and primaryinfo need to be set
## C_HA indicates centralized high available version: configuration information of primaryinfo, standbyinfo, etcdinfo, patroniinfo needs to be set
## cluster_name: name of the database cluster
## cluster_user: The superuser of the database, usually is the operating system user who executes this installer

[clusterinfo]
cluster_type = C_HA ###change the cluster type as C_HA
cluster_name = antdbcluster
cluster_user = antdb


## primaryinfo configuration description:
##
## antdb_apppath: the program directory of primary node database
## antdb_datapath: the data directory of the primary node database; it needs to be set as an empty directory and not crossed with the directories in other configuration items
## antdb_password: the initial password for the superuser of the database (see "cluster_user" for the superuser)
## antdb_port: the port number of the primary node database
## primary_ip: the primary node database ip, i.e. the host ip where this installer is executed
## primary_sshport: the SSH service port number of the host executing this installer

[primary_info]
primary_ip = 192.168.37.130 ###Modify to the current host IP address
primary_sshport = 22
antdb_apppath = /home/antdb/app/antdb ###antdb software directory, modify it to the current antdb software directory
antdb_datapath = /home/antdb/data ### antdb data directory
antdb_password = antdb
antdb_port = 6655 ###You can customize the port, here choose the default 6655


## standbyinfo configuration item description:
##
## standby_node format: name,standby_ip,standby_sshport,antdb_apppath,antd b_datapath,antdb_port
## name: the name of the standby node, only as an identifier, unique
## standby_ip: the ip address of the standby node
## standby_sshport: the SSH service port number of the standby node
## antdb_apppath: the directory where the standby node stores the database application, it is recommended to use the same path as the primary node
## antdb_datapath: the directory where the standby node stores database data, it is recommended to use the same path as the primary node
## antdb_port: the port number of the standby node database

[standby_info]
standby_node = standby1,192.168.37.131,22,/home/antdb/app/antdb,/home/antdb/data,6655 ### the IP address is changed to the IP address of the corresponding standby database, and the rest remains unchanged.
standby_node = standby2,192.168.37.131,22,/home/antdb/app/antdb,/home/antdb/data,6655 ### the IP address is changed to the IP address of the corresponding standby database, and the rest remains unchanged.


## etcd_info configuration item description:
##
## etcd_node format: name,etcd_datapath,clienport,peerport,hostinfo
## name: the name of etcd node, unique
## etcd_datapath: the etcd data directory, do not cross with database data directory
## clienport: the port number used by client to access etcd
## peerport: the etcd communication port number
## hostinfo: database node name, primary means primary node, others are standby node names; it identifies which database node is on the same node as etcd

[etcd_info]
etcd_node = etcd-1,/home/antdb/etcd,12379,12380,primary
etcd_node = etcd-2,/home/antdb/etcd,12379,12380,standby1
etcd_node = etcd-3,/home/antdb/etcd,12379,12380,standby2


## patroni_info configuration item description:
##
## patroni_node format: name,patroni_port,hostinfo
## name: the name of patroni node, unique
## patroni_port: the port number used by the patroni service
## hostinfo: database node name, primary means primary node, others are standby node names; it identifies which database node is located on the same node aspatroni

[patroni_info]
patroni_node = patroni-1,8008,primary
patroni_node = patroni-2,8008,standby1
patroni_node = patroni-3,8008,standby2

5). Execute initialization
sh antdb_init.sh -c ./setup/common/initconf-c.ini

...
...

AntDB init succeeds appears, the centralized highly available version is deployed.

6). After deployment, antdb will dynamically adjust the OS parameter limits, resource usage limits, and database parameters according to the server resource configuration

cat /etc/security/limits.conf ###resource limits

database parameters

7). High Availability Test
Using adb_list, you can view the cluster status

The native patronictl command can also be used for that purpose

Execute cluster switch, the master of the cluster switched from 130 to 132