Databases 14 min read

Step-by-Step Guide to Installing GaussDB T 1.0.2 HA Cluster on CentOS

This tutorial walks you through preparing the environment, configuring cluster components, installing required packages, setting up Python 3.7, running pre‑install checks, executing the GaussDB installation script, handling common errors, and finally uninstalling the cluster on a CentOS 7.5 system.

dbaplus Community
dbaplus Community
dbaplus Community
Step-by-Step Guide to Installing GaussDB T 1.0.2 HA Cluster on CentOS

Overview

GaussDB T 1.0.2 (GA version) introduces improved stability and new features over 1.0.1, with a forthcoming RAC version. The article explains how to deploy a primary‑standby (one‑master‑one‑standby) cluster without a CN, where the DN host acts as the master node.

Cluster Component Roles

CM : Cluster Manager, monitors and controls all functional units and physical resources.

DN : Datanode, stores business data, processes queries, and returns results.

ETCD : Distributed key‑value store that keeps cluster state for CM.

Storage : Local server storage for persistent data.

Environment Preparation

Operating System: CentOS Linux release 7.5.1804 (Core)

Database package:

GaussDB_T_1.0.2-CLUSTER-CentOS-64bit.tar.gz

Installation Steps

Enable root SSH login

sed -i 's/#PermitRootLogin yes/PermitRootLogin yes/g' /etc/ssh/sshd_config
sed -i 's/#PasswordAuthentication yes/PasswordAuthentication yes/g' /etc/ssh/sshd_config
/bin/systemctl restart sshd.service

Disable firewall and SELinux

systemctl stop firewalld.service
systemctl disable firewalld.service
sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

Configure core dump limits

echo 'ulimit -c unlimited' >> /etc/profile
echo 'kernel.core_pattern =/opt/gdb/corefile/core-%e-%p-%t' >> /etc/sysctl.conf
source /etc/profile
sysctl -p

Check NTP and lsof

rpm -qa|grep ntp   # if missing, yum install ntp
which lsof        # if missing, yum install lsof

Create installation user and group

groupadd dbgrp
useradd -g dbgrp -d /home/omm -m -s /bin/bash omm
passwd omm

Prepare software directory and extract packages

mkdir -p /opt/software/gaussdb
cd /opt/software/gaussdb
tar -zxvf GaussDB_T_1.0.2-CENTOS7.5-X86.tar.gz
chmod 755 /opt/software/
chmod -R 755 /opt/software/gaussdb/

Modify the provided clusterconfig.xml template Edit /opt/software/gaussdb/clusterconfig.xml to reflect actual node names, IPs, ETCD ports, and other parameters (e.g., nodeNames , GatewayIP , cmServerRelation ).

Install Python 3.7 (if not present)

yum -y groupinstall "Development tools"
yum -y install zlib-devel bzip2-devel openssl-devel ncurses-devel sqlite-devel readline-devel tk-devel gdbm-devel libpcap-devel xz-devel libffi-devel gcc
cd /root
wget https://www.python.org/ftp/python/3.7.0/Python-3.7.0.tar.xz
tar -xvJf Python-3.7.0.tar.xz
mkdir /usr/local/python3
cd Python-3.7.0
./configure --prefix=/usr/local/python3
make && make install
ln -s /usr/local/python3/bin/python3 /usr/local/bin/python3
python3 -V
pip3 -V

Run pre‑install script

cd /opt/software/gaussdb/script/
./gs_preinstall -U omm -G dbgrp -X /opt/software/gaussdb/clusterconfig.xml

Check cluster time consistency

./gs_checkos -i B -h gauss1,gauss2 -X /opt/software/gaussdb/clusterconfig.xml

Execute the installation script

su - omm
gs_install -X /opt/software/gaussdb/clusterconfig.xml

Verify cluster status Use the provided UI or gs_checkos commands to confirm all components are running.

Error Handling During Installation

GAUSS‑50204 : Failed to read cmServerRelation. Fix by ensuring cmServerRelation in clusterconfig.xml matches the order of nodeNames (e.g., gauss2,gauss1).

GAUSS‑53011 : Invalid GatewayIP. Update GatewayIP to the correct virtual‑machine gateway address (e.g., 192.168.238.2).

Time consistency warnings : Synchronize system clocks on all nodes before re‑running gs_checkos.

Cluster Uninstallation

From the omm user run:

gs_uninstall --delete-data -X /opt/software/gaussdb/clusterconfig.xml

Clean host environment with:

./gs_postuninstall -U omm -X /opt/software/gaussdb/clusterconfig.xml

After successful uninstallation, close the terminal and log in again to apply cleaned environment variables.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

InstallationetcdHACentOSShell CommandsDatabase ClusterGaussDB
dbaplus Community
Written by

dbaplus Community

Enterprise-level professional community for Database, BigData, and AIOps. Daily original articles, weekly online tech talks, monthly offline salons, and quarterly XCOPS&DAMS conferences—delivered by industry experts.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.