Cluster ETCD

• hostname : Node-esql01
  • IP : 192.168.1.100/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1
• hostname : Node-esql02
  • IP : 192.168.1.101/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1
• hostname : Node-esql03
  • IP : 192.168.1.102/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1

1. Mise à jour (3 nodes)

[root@node-esql0x ~]# dnf update -y

2. Ajout des Hosts (pas de DNS)

Nodes ETCD

[root@node-esql01 ~]# echo "# Cluster ETCD " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.100 node-esql01 " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.101 node-esql02 " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.102 node-esql03 " >> /etc/hosts

Nodes PostgreSQL

[root@node-esql01 ~]# echo "# Cluster PostgreSQL " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.103 node-psql01 " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.104 node-psql02 " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.105 node-psql03 " >> /etc/hosts

Nodes HaProxy

[root@node-esql01 ~]# echo "# Cluster HaProxy " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.106 node-hsql01 " >> /etc/hosts
[root@node-esql01 ~]# echo "192.168.1.107 node-hsql02 " >> /etc/hosts

[root@node-esql01 ~]# cat /etc/hosts

Copy de /etc/hosts vers les hosts

[root@node-esql01 ~]# scp /etc/hosts root@node-esql02:/etc/hosts
[root@node-esql01 ~]# scp /etc/hosts root@node-esql03:/etc/hosts

Check résolution hosts

[root@node-esql0x ~]# ping -c 2 node-esql01
[root@node-esql0x ~]# ping -c 2 node-esql02
[root@node-esql0x ~]# ping -c 2 node-esql03

3. Désactiver SELinux (3 nodes)

[root@node-esql0x ~]# getenforce
Enforcing

[root@node-esql0x ~]# setenforce 0
[root@node-esql0x ~]# getenforce
Permissive

[root@node-esql0x ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

4. Synchroniser DateTime sur le fuseau de PARIS (3 nodes)

[root@node-esql0x ~]# timedatectl

[root@node-esql0x ~]# timedatectl set-timezone Europe/Paris

[root@node-esql0x ~]# timedatectl

5. Installation des middlewares (3 nodes)

[root@node-esql0x ~]# dnf install epel-release net-tools nmap curl wget tar -y

6. Installation Cluster etcd (3 nodes)

Installation Repository etcd

[root@node-esql0x ~]# echo "ETCD_RELEASE=$(curl -s https://api.github.com/repos/etcd-io/etcd/releases/latest|grep tag_name | cut -d '"' -f 4)" >> ~/.bashrc
[root@node-esql0x ~]# source ~/.bashrc
[root@node-esql0x ~]# echo $ETCD_RELEASE
v3.5.7 

[root@node-esql0x ~]# cd /tmp && wget https://github.com/etcd-io/etcd/releases/download/${ETCD_RELEASE}/etcd-${ETCD_RELEASE}-linux-amd64.tar.gz

[root@node-esql0x ~]# ls -al |grep etc

Installation binaire etcd

[root@node-esql0x ~]# tar -xzvf etcd-${ETCD_RELEASE}-linux-amd64.tar.gz
[root@node-esql0x ~]# cd etcd-${ETCD_RELEASE}-linux-amd64/

[root@node-esql0x etcd-v3.5.7-linux-amd64]# ls -al |grep etc |grep -v READ

[root@node-esql0x etcd-v3.5.7-linux-amd64]# mv etcd* /usr/local/bin

[root@node-esql0x etcd-v3.5.7-linux-amd64]# ls /usr/local/bin

[root@node-esql0x etcd-v3.5.7-linux-amd64]# etcd --version
[root@node-esql0x etcd-v3.5.7-linux-amd64]# etcdctl version
[root@node-esql0x etcd-v3.5.7-linux-amd64]# etcdutl version

7. Installation/création de la structure ETCD

Création de la strucure etcd

[root@node-esql0x etcd-v3.5.7-linux-amd64]# cd ~
[root@node-esql0x ~]# mkdir -p /var/lib/etcd/
[root@node-esql0x ~]# mkdir /etc/etcd

Création droit user/group etcd

[root@node-esql0x ~]# groupadd --system etcd
[root@node-esql0x ~]# useradd -s /sbin/nologin --system -g etcd etcd

Ajout des droits user/group etcd sur la structure

[root@node-esql0x ~]# chown -R etcd:etcd /var/lib/etcd/
[root@node-esql0x ~]# chmod -R 0700 /var/lib/etcd

Ouverture des rules Firewall

[root@node-esql0x ~]# firewall-cmd --zone=public --permanent --add-port={2379,2380}/tcp
[root@node-esql0x ~]# firewall-cmd --remove-service={cockpit,dhcpv6-client} --permanent
[root@node-esql0x ~]# firewall-cmd --reload
[root@node-esql0x ~]# firewall-cmd --list-port
2379/tcp 2380/tcp 

[root@node-esql0x ~]# firewall-cmd --list-all

8. Configuration du cluster etcd

Création du Service etcd  node-esql01

[root@node-esql01 ~]# systemctl stop etcd.service

[root@node-esql01 ~]# vi /etc/systemd/system/etcd.service

[Unit]
Description=etcd key-value store
Documentation=https://github.com/etcd-io/etcd
After=network.target

[Service]
User=etcd
Type=notify
ExecStart=/usr/local/bin/etcd \
--name node-esql01 \
--data-dir /var/lib/etcd/node-esql01 \
--initial-advertise-peer-urls http://192.168.1.100:2380 \
--listen-peer-urls http://192.168.1.100:2380 \
--listen-client-urls http://192.168.1.100:2379,http://127.0.0.1:2379 \
--advertise-client-urls http://192.168.1.100:2379 \
--initial-cluster-token clusterpsql \
--initial-cluster node-esql01=http://192.168.1.100:2380 \
--initial-cluster-state new \
--heartbeat-interval 1000 \
--election-timeout 5000 \
--enable-v2
Restart=always
RestartSec=10s
LimitNOFILE=40000

[Install]
WantedBy=multi-user.target

On recharge le service

[root@node-esql01 ~]# systemctl daemon-reload

Création du Service etcd  node-esql02

[root@node-esql02 ~]# systemctl stop etcd.service

[root@node-esql02 ~]# vi /etc/systemd/system/etcd.service

[Unit]
Description=etcd key-value store
Documentation=https://github.com/etcd-io/etcd
After=network.target

[Service]
User=etcd
Type=notify
ExecStart=/usr/local/bin/etcd \
--name node-esql02 \
--data-dir /var/lib/etcd/node-esql02 \
--initial-advertise-peer-urls http://192.168.1.101:2380 \
--listen-peer-urls http://192.168.1.101:2380 \
--listen-client-urls http://192.168.1.101:2379,http://127.0.0.1:2379 \
--advertise-client-urls http://192.168.1.101:2379 \
--initial-cluster-token clusterpsql \
--initial-cluster node-esql01=http://192.168.1.100:2380,node-esql02=http://192.168.1.101:2380 \
--initial-cluster-state existing \
--heartbeat-interval 1000 \
--election-timeout 5000 \
--enable-v2
Restart=always
RestartSec=10s
LimitNOFILE=40000

[Install]
WantedBy=multi-user.target

On recharge le service

[root@node-esql02 ~]# systemctl daemon-reload

Création du Service etcd  node-esql03

[root@node-esql03 ~]# systemctl stop etcd.service

[root@node-esql03 ~]# vi /etc/systemd/system/etcd.service

[Unit]
Description=etcd key-value store
Documentation=https://github.com/etcd-io/etcd
After=network.target

[Service]
User=etcd
Type=notify
ExecStart=/usr/local/bin/etcd \
--name node-esql03 \
--data-dir /var/lib/etcd/node-esql03 \
--initial-advertise-peer-urls http://192.168.1.102:2380 \
--listen-peer-urls http://192.168.1.102:2380 \
--listen-client-urls http://192.168.1.102:2379,http://127.0.0.1:2379 \
--advertise-client-urls http://192.168.1.102:2379 \
--initial-cluster-token clusterpsql \
--initial-cluster node-esql01=http://192.168.1.100:2380,node-esql02=http://192.168.1.101:2380,node-esql03=http://192.168.1.102:2380 \
--initial-cluster-state existing \
--heartbeat-interval 1000 \
--election-timeout 5000 \
 --enable-v2
Restart=always
RestartSec=10s
LimitNOFILE=40000

[Install]
WantedBy=multi-user.target

On recharge le service

[root@node-psql03 ~]# systemctl daemon-reload

9. Lancement du cluster etcd

Lancement etcd sur node-esql01

On supprime des anciennes traces d’installation cluster

[root@node-esql01 ~]# rm -rf /var/lib/etcd/node-esql01
[root@node-esql01 ~]# systemctl start etcd.service

[root@node-esql01 ~]# systemctl status etcd.service

Ajout des membres du cluster sur node-esql01

[root@node-esql01 ~]# etcdctl member add node-esql02 --peer-urls=http://192.168.1.101:2380

[root@node-esql01 ~]# etcdctl member add node-esql03 --peer-urls=http://192.168.1.102:2380

Démarrage/Création du Cluster ETCD

Lancement etcd node-esql01

[root@node-esql01 ~]# systemctl start --now etcd
[root@node-esql01 ~]# systemctl enable etcd.service

Lancement etcd node-esql02

[root@node-esql02 ~]# systemctl start --now etcd
[root@node-esql02 ~]# systemctl enable etcd.service

Lancement etcd node-esql03

[root@node-esql03 ~]# systemctl start --now etcd
[root@node-esql03 ~]# systemctl enable etcd.service

10. Check du Cluster ETCD

Check « Status » des membres

[root@node-esql01 ~]# etcdctl -w table member list

Check « Health » des membres

[root@node-esql01 ~]# etcdctl endpoint health --endpoints=192.168.1.100:2380,192.168.1.101:2380,192.168.1.101:2380 health

[root@node-esql01 ~]# etcdctl --write-out=table --endpoints=192.168.1.100:2380,192.168.1.101:2380,192.168.1.101:2380 endpoint status

Views: 8

L’article MODOP – Partie 1 – PostgreSQL HA – Installation du Cluster ETCD est apparu en premier sur CoffeeBreak Info.

Cluster HaProxy

• hostname : Node-hsql01
  • IP : 192.168.1.106/24
  • VIP : 192.168.1.110/24
    • Virtuel Host : node-sql
  • RAM : 2Go
  • CPU : 1
• hostname : Node-hsql02
  • IP : 192.168.1.107/24
  • VIP : 192.168.1.110/24
    • Virtuel Host : node-sql
  • RAM : 2Go
  • CPU : 1

1. Mise à jour (2 nodes)

[root@node-hsql0x ~]# dnf update -y

2. Ajout des Hosts (pas de DNS)

Copy de /etc/hosts node-esql01 vers les hosts hsql

[root@node-hsql01 ~]# scp root@192.168.1.100:/etc/hosts /etc/hosts
[root@node-hsql02 ~]# scp root@192.168.1.100:/etc/hosts /etc/hosts
[root@node-hsql0x ~]# cat /etc/hosts

Check résolution hosts (2 hosts)

[root@node-hsql0x ~]# ping -c 2 node-esql01
[root@node-hsql0x ~]# ping -c 2 node-psql01
[root@node-hsql0x ~]# ping -c 2 node-hsql02

3. Désactiver SELinux (2 nodes)

[root@node-hsql0x ~]# setenforce 0
[root@node-psql0x ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

4. Synchroniser DateTime sur le fuseau de PARIS (2 nodes)

[root@node-hsql0x ~]# timedatectl set-timezone Europe/Paris

5. Installation des middlewares (2 nodes)

[root@node-hsql0x ~]# dnf install epel-release net-tools nmap curl wget tar –y

6. Installation KeepAlive (2 nodes)

Installation des paquets

[root@node-hsql0x ~]# dnf -y install keepalived
[root@node-hsql0x ~]# dnf -y install ipvsadm

Chargement du module ip_vs

[root@node-hsql0x ~]# modprobe ip_vs
[root@node-hsql0x ~]# lsmod |grep ip_vs

[root@node-hsql0x ~]# echo ip_vs >> /etc/module

Configuration KeepAlive

[root@node-hsql0x ~]# cp /etc/keepalived/keepalived.conf{,-old}
[root@node-hsql0x ~]# sh -c '> /etc/keepalived/keepalived.conf'

Fichier conf node-hsql01

[root@node-hsql01 ~]# vi /etc/keepalived/keepalived.conf

! /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
 notification_email {
 chris@en-images.info
 }

 notification_email_from chris@en-images.info
 smtp_server localhost
 smtp_connect_timeout 30
 }

vrrp_instance VI_1 {
 state MASTER
 interface ens18
 virtual_router_id 100
 priority 200

 authentication {
auth_type PASS
 auth_pass chris@2023
 }

 virtual_ipaddress {
 192.168.1.110/24 dev ens18
 }

}

Fichier conf node-hsql02

[root@node-hsql02 ~]# vi /etc/keepalived/keepalived.conf

! /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
notification_email {
chris@en-images.info
}

 notification_email_from chris@en-images.info
 smtp_server localhost
 smtp_connect_timeout 30

}

vrrp_instance VI_1 {
 state BACKUP
 interface ens18
 virtual_router_id 100
 priority 199

authentication {
 auth_type PASS
 auth_pass chris@2023
}

virtual_ipaddress {
192.168.1.110/24 dev ens18
}

}

Prérequis réseau KeepAlive

[root@node-hsql0x ~]# echo "net.ipv4.ip_nonlocal_bind = 1" >> /etc/sysctl.conf
[root@node-hsql0x ~]# sysctl -p
net.ipv4.ip_nonlocal_bind = 1

Règles firewall

[root@node-hsql0x ~]# firewall-cmd --add-rich-rule='rule protocol value="vrrp" accept' --permanent --zone=public
[root@node-hsql0x ~]# firewall-cmd --remove-service={cockpit,dhcpv6-client} --permanent
[root@node-hsql0x ~]# firewall-cmd --reload

Lancement KeepAlive

Node-hsql01

[root@node-hsql01 ~]# systemctl start --now keepalived
[root@node-hsql01 ~]# systemctl enable keepalived

[root@node-hsql01 ~]# systemctl status keepalived

[root@node-hsql01 ~]# ip a

Node-hsql02

[root@node-hsql02 ~]# systemctl start --now keepalived
[root@node-hsql02 ~]# systemctl enable keepalived

[root@node-hsql02 ~]# systemctl status keepalived

[root@node-hsql02 ~]# ip a

7. Installation client postgreSQL ( 2 nodes)

Installation Repository PostgreSQL

[root@node-hsql0x ~]# dnf -y install yum-utils
[root@node-hsql0x ~]# dnf -y install https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat-repo-latest.noarch.rpm

Sélection version 12 PostgreSQL

[root@node-hsql0x ~]# dnf -y module list postgresql
[root@node-hsql0x ~]# dnf -y module enable postgresql:12

Installation du paquet client de postgresql

[root@node-hsql0x ~]# dnf -qy module disable postgresql
[root@node-hsql0x ~]# dnf -y install postgresql12
[root@node-hsql0x ~]# ls /usr/pgsql-12/bin
[root@node-hsql0x ~]# ln -s /usr/pgsql-12/bin/* /usr/sbin/

8. Installation HaProxy (2 nodes)

Installation du paquet

[root@node-hsql0x ~]# dnf install -y haproxy

Inventaire des ports Utiles

• Port 5000 : « Writes SQL»
• Port 5001 : « Read SQL»
• Port 7000 : « DashBoard HaProxy »
• Port 8008 : « Patroni Rest api »
• Port 5432 : PostgreSQL

Check Accès Cluster Psql

Check rest api patroni

[root@node-hsql01 ~]# curl -s http://node-psql01:8008

[root@node-hsql01 ~]# curl -s http://node-psql02:8008
[root@node-hsql01 ~]# curl -s http://node-psql03:8008

Check connexion postgreSQL via les nodes HaProxy

[root@node-hsql01 ~]# psql -U chris -h node-psql01 -d chris2023

[root@node-hsql01 ~]# psql -U chris -h node-psql02 -d chris2023
[root@node-hsql01 ~]# psql -U chris -h node-psql03 -d chris2023

Configuration HaProxy ( 2 nodes)

[root@node-hsql0x ~]# mv /etc/haproxy/haproxy.cfg{,-old}

[root@node-hsql0x ~]# vi /etc/haproxy/haproxy.cfg

global
 maxconn 100
defaults
 log global
 mode tcp
 retries 2
 timeout client 30m
 timeout connect 4s
 timeout server 30m
 timeout check 5s

listen stats
 mode http
 bind *:7000
 stats enable
 stats uri /status
 stats refresh 2s
 stats auth chris:Chris
 stats admin if TRUE

listen master
 bind *:5000
 option httpchk OPTIONS /master
 http-check expect status 200
 default-server inter 3s fall 3 rise 2 on-marked-down shutdown-sessions
 server node-psql01 node-psql01:5432 maxconn 100 check port 8008
 server node-psql02 node-psql02:5432 maxconn 100 check port 8008
 server node-psql03 node-psql03:5432 maxconn 100 check port 8008

listen replicats
 balance roundrobin
 bind *:5001
 option httpchk OPTIONS /replica
 http-check expect status 200
 default-server inter 3s fall 3 rise 2 on-marked-down shutdown-sessions
 server node-psql01 node-psql01:5432 maxconn 100 check port 8008
 server node-psql02 node-psql02:5432 maxconn 100 check port 8008
 server node-psql03 node-psql03:5432 maxconn 100 check port 8008

[root@node-hsql0x ~]# haproxy -c -V -f /etc/haproxy/haproxy.cfg
Configuration file is valid

Régles Firewall (2 nodes)

[root@node-hsql0x ~]# firewall-cmd --add-port={5000,5001,7000}/tcp --permanent
[root@node-hsql0x ~]# firewall-cmd --add-service=http –permanent
[root@node-hsql0x ~]# firewall-cmd --reload

Démarrage du service HaProxy (2 nodes)

[root@node-hsql0x ~]# systemctl start haproxy
[root@node-hsql0x ~]# systemctl enable haproxy

[root@node-hsql0x ~]# systemctl status haproxy

9. Connexion IHM HaProxy

• http://192.168.1.110:7000/status

Login/passwod : chris/Chris

Ici on peut constater les deux configurations suivantes

• Le master « Write SQL » est le node-psql02
• Les réplicas « Read SQL » sont node-psql01 et node-psql03

Views: 8

L’article MODOP – Partie 3 – PostrgreSQL – Installation du Cluster HaPoxy est apparu en premier sur CoffeeBreak Info.

Cluster PostgreSQL/patroni

• hostname : Node-psql01
  • IP : 192.168.1.103/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1
• hostname : Node-psql02
  • IP : 192.168.1.104/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1
• hostname : Node-psql03
  • IP : 192.168.1.105/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1

1. Mise à jour (3 nodes)

[root@node-psql0x ~]# dnf update -y

2. Ajout des Hosts (pas de DNS)

Copy de /etc/hosts node-esql01 vers les hosts psql

[root@node-psql01 ~]# scp root@192.168.1.100:/etc/hosts /etc/hosts
[root@node-psql02 ~]# scp root@192.168.1.100:/etc/hosts /etc/hosts
[root@node-psql03 ~]# scp root@192.168.1.100:/etc/hosts /etc/hosts

[root@node-psql0x ~]# cat /etc/hosts

Check résolution hosts

[root@node-psql0x ~]# ping -c 2 node-esql01
[root@node-psql0x ~]# ping -c 2 node-psql01
[root@node-psql0x ~]# ping -c 2 node-hsql01

3. Désactiver SELinux (3 nodes)

[root@node-psql0x ~]# setenforce 0
[root@node-psql0x ~]# getenforce
Permissive
[root@node-psql0x ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

4. Synchroniser DateTime sur le fuseau de PARIS (3 nodes)

[root@node-psql0x ~]# timedatectl set-timezone Europe/Paris
[root@node-psql0x ~]# timedatectl

5. Installation des middlewares (3 nodes)

[root@node-esql0x ~]# dnf install epel-release net-tools nmap curl wget tar -y

6. Installation Cluster PostgreSQL v12 (3 nodes)

Installation Repository PostgreSQL

[root@node-psql0x ~]# dnf -y install yum-utils
[root@node-psql0x ~]# dnf -y install https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat-repo-latest.noarch.rpm

Installation PostgreSQL v12

[root@node-psql0x ~]# dnf module list postgresql

[root@node-psql0x ~]# dnf module enable postgresql:12

[root@node-psql0x ~]# dnf --enablerepo=powertools install perl-IPC-Run
[root@node-psql0x ~]# dnf -qy module disable postgresql

[root@node-psql0x ~]# dnf -y install postgresql12 postgresql12-server postgresql12-devel

[root@node-psql0x ~]# ls /usr/pgsql-12/bin
[root@node-psql0x ~]# ln -s /usr/pgsql-12/bin/* /usr/sbin/

7. Installation Patroni (3 nodes)

Installation des prérequis (3 nodes)

[root@node-psql0x ~]# dnf -y install python3 python3-devel python3-pip gcc libpq-devel
[root@node-psql0x ~]# pip3 install --upgrade testresources
[root@node-psql0x ~]# pip3 install --upgrade setuptools

Installation patroni et dépendances (3 nodes)

[root@node-psql0x ~]# pip3 install psycopg2
[root@node-psql0x ~]# dnf -y install python3-etcd
[root@node-psql0x ~]# dnf -y install patroni patroni-etcd watchdog

Configuration patroni (3 nodes)

[root@node-psql0x ~]# mkdir -p /etc/patroni
[root@node-psql0x ~]# cp -v /usr/share/doc/patroni/postgres0.yml /etc/patroni/patroni.yml
'/usr/share/doc/patroni/postgres0.yml' -> '/etc/patroni/patroni.yml'

Configuration patroni – node-psql01

[root@node-psql01 ~]# vi /etc/patroni/patroni.yml

scope: psql_cluster
namespace: /service/
name: node-psql01

restapi:
 listen: 0.0.0.0:8008
 connect_address: 192.168.1.103:8008

etcd:
 hosts:
 - 192.168.1.100:2379
 - 192.168.1.101:2379
 - 192.168.1.102:2379

bootstrap:
 dcs:
 ttl: 30
 loop_wait: 10
 retry_timeout: 10
 maximum_lag_on_failover: 1048576

 postgresql:
 use_pg_rewind: true
 use_slots: true
 parameters:

 initdb:
 - encoding: UTF8
 - data-checksums

 pg_hba: # Add following lines to pg_hba.conf after running 'initdb'
 - host replication replicator 127.0.0.1/32 md5
 - host replication replicator 192.168.1.103/0 md5
 - host replication replicator 192.168.1.104/0 md5
 - host replication replicator 192.168.1.105/0 md5
 - host all all 0.0.0.0/0 md5
 - host all all 192.168.1.0/24 md5

 users:
 admin:
 password: admin
 options:
 - createrole
 - createdb

postgresql:
 listen: 192.168.1.103:5432
 connect_address: 192.168.1.103:5432
 data_dir: /var/lib/pgsql/12/data
 bin_dir: /usr/pgsql-12/bin
 pgpass: /tmp/pgpass

 authentication:
 replication:
 username: replicator
 password: replicator2023
 superuser:
username: postgres
 password: chris@2023

watchdog:
 mode: required
 device: /dev/watchdog
 safety_margin: 5

tags:
 nofailover: false
 noloadbalance: false
 clonefrom: false
 nosync: false

Configuration patroni – node-esql02

[root@node-psql02 ~]# vi /etc/patroni/patroni.yml

scope: psql_cluster
namespace: /service/
name: node-psql02

restapi:
 listen: 0.0.0.0:8008
 connect_address: 192.168.1.104:8008

etcd:
 hosts:
 - 192.168.1.100:2379
 - 192.168.1.101:2379
 - 192.168.1.102:2379

bootstrap:
 dcs:
 ttl: 30
 loop_wait: 10
 retry_timeout: 10
 maximum_lag_on_failover: 1048576

 postgresql:
 use_pg_rewind: true
 use_slots: true

 parameters:
 initdb:
 - encoding: UTF8
 - data-checksums

 pg_hba: # Add following lines to pg_hba.conf after running 'initdb'
 - host replication replicator 127.0.0.1/32 md5
 - host replication replicator 192.168.1.103/0 md5
 - host replication replicator 192.168.1.104/0 md5
 - host replication replicator 192.168.1.105/0 md5
 - host all all 0.0.0.0/0 md5
 - host all all 192.168.1.0/24 md5

 users:
 admin:
 password: admin
 options:
 - createrole
 - createdb

postgresql:
 listen: 0.0.0.0:5432
 connect_address: 192.168.1.104:5432
 data_dir: /var/lib/pgsql/12/data
 bin_dir: /usr/pgsql-12/bin
 pgpass: /tmp/pgpass

 authentication:
 replication:
 username: replicator
 password: replicator2023
 superuser:
username: postgres
 password: chris@2023

watchdog:
 mode: required
 device: /dev/watchdog
 safety_margin: 5

tags:
 nofailover: false
 noloadbalance: false
 clonefrom: false
 nosync: false

Configuration patroni – node-esql03

[root@node-psql03 ~]# vi /etc/patroni/patroni.yml

scope: psql_cluster
namespace: /service/
name: node-psql03

restapi:
 listen: 0.0.0.0:8008
 connect_address: 192.168.1.105:8008

etcd:
 hosts:
 - 192.168.1.100:2379
 - 192.168.1.101:2379
 - 192.168.1.102:2379

bootstrap:
 dcs:
 ttl: 30
 loop_wait: 10
 retry_timeout: 10
 maximum_lag_on_failover: 1048576

 postgresql:
 use_pg_rewind: true
 use_slots: true

 parameters:
 initdb:
 - encoding: UTF8
 - data-checksums

 pg_hba: # Add following lines to pg_hba.conf after running 'initdb'
 - host replication replicator 127.0.0.1/32 md5
 - host replication replicator 192.168.1.103/0 md5
 - host replication replicator 192.168.1.104/0 md5
 - host replication replicator 192.168.1.105/0 md5
 - host all all 0.0.0.0/0 md5
 - host all all 192.168.1.0/24 md5

 users:
 admin:
 password: admin
 options:
 - createrole
 - createdb

postgresql:
 listen: 0.0.0.0:5432
 connect_address: 192.168.1.105:5432
 data_dir: /var/lib/pgsql/12/data
 bin_dir: /usr/pgsql-12/bin
 pgpass: /tmp/pgpass

 authentication:
 replication:
 username: replicator
 password: replicator2023
 superuser:
username: postgres
 password: chris@2023

watchdog:
 mode: required
 device: /dev/watchdog
 safety_margin: 5

tags:
 nofailover: false
 noloadbalance: false
 clonefrom: false
 nosync: false

8. Activation Watchdogs pour postgres (3 nodes)

[root@node-psql0x ~]# vi /etc/watchdog.conf

Dé-commenter la ligne « watchdog-device »

[root@node-psql0x ~]# mknod /dev/watchdog c 10 130
[root@node-psql0x ~]# modprobe softdog
[root@node-psql0x ~]# chown postgres /dev/watchdog

[root@node-psql0x ~]# ls -al /dev/watchdog

9. Règles firewall (3 nodes)

[root@node-psql0x ~]# firewall-cmd --zone=public --add-port=8008/tcp --permanent
[root@node-psql0x ~]# firewall-cmd --zone=public --add-port=5432/tcp --permanent
[root@node-psql0x ~]# firewall-cmd --remove-service={cockpit,dhcpv6-client} –permanent
[root@node-psql0x ~]# firewall-cmd --reload

[root@node-psql0x ~]# firewall-cmd --list-all

10. Lancement de Patroni (3 nodes)

Node-psql01

[root@node-psql01 ~]# systemctl start patroni
[root@node-psql01 ~]# systemctl enable patroni

[root@node-psql01 ~]# systemctl status patroni

Node-psql02

[root@node-psql02 ~]# systemctl start patroni
[root@node-psql02 ~]# systemctl enable patroni

[root@node-psql02 ~]# systemctl status patroni

Node-psql03

[root@node-psql03 ~]# systemctl start patroni
[root@node-psql03 ~]# systemctl enable patroni

[root@node-psql03 ~]# systemctl status patroni

11. Check cluster Patroni

[root@node-psql01 ~]# patronictl -d etcd://192.168.1.100:2379 list psql_cluster

[root@node-psql01 ~]# curl -s http://node-psql01:8008

[root@node-psql01 ~]# curl -s http://node-psql02:8008

[root@node-psql01 ~]# curl -s http://node-psql03:8008

12. Check cluster SQL HA

Création données sur Node-psql01 (node Master)

[root@node-psql01 ~]# psql -U postgres
postgres-# \du

postgres=# SELECT schema_name FROM information_schema.schemata;

postgres=# CREATE DATABASE chris2023;
CREATE DATABASE

postgres=# \l

postgres=# CREATE ROLE chris SUPERUSER LOGIN PASSWORD 'chris2023';
CREATE ROLE

postgres=# \du

Check réplication données sur Node-psql02 et node-psql03 ( replication)

[root@node-psql0x~]# psql -U postgres
postgres=# \du

postgres=# \l

Views: 4

L’article MODOP – Partie 2 – PostgreSQL HA – Installation du Cluster PostgreSQL/Patroni est apparu en premier sur CoffeeBreak Info.

[root@node-csql ~]# dnf update -y

2. Ajout hosts VIP node-sql

[root@node-csql ~]# echo "192.168.1.110 node-sql" >> /etc/hosts

[root@node-csql ~]# ping -c 2 node-sql

3. Désactiver SELinux

[root@node-csql ~]# setenforce 0
[root@node-csql ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

4. Synchroniser DateTime sur le fuseau de PARIS

[root@node-csql ~]# timedatectl set-timezone Europe/Paris

5. Installation client PostgreSQL

[root@node-csql ~]# dnf -y install postgresql.x86_64

6. Requête SQL sur Serveur « Write » port 5000

Qui est serveur « Master » sur le cluster

[root@node-csql ~]# echo "node-sql:5000:chris2023:chris:chris2023" >> ~/.pgpass
[root@node-csql ~]# chmod 0600 ~/.pgpass

[root@node-csql ~]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "select inet_server_addr()"
192.168.1.104

Ici le serveur « Master » est le node-psql02 (192.168.1.104)

Création d’une base « betty » via node-psql02

[root@node-csql ~]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "CREATE DATABASE betty"
CREATE DATABASE

Création utilisateur « bettyboop » via node-psql02

[root@node-csql ~]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "CREATE USER bettyboop WITH PASSWORD 'betty2023'"
CREATE ROLE

Liste des bases sur le node-psql02

[root@node-csql ~]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "\l"

Liste des utilisateurs sur le node-psql02

[root@node-csql ~]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "\du"

7. Requête SQL sur Serveur « Write » port 5001

Qui est serveur « Replicator » sur le cluster

[root@node-csql ~]# echo "node-sql:5001:chris2023:chris:chris2023" >> ~/.pgpass
[root@node-csql ~]# chmod 0600 ~/.pgpass

[root@node-csql ~]# for i in {1..4}; do psql -U chris -h node-sql -p 5001 -d chris2023 -t -c "select inet_server_addr()" ; done

Création d’une base « betty » via les nodes de réplication (READ)

[root@node-csql ~]# psql -U chris -h node-sql -p 5001 -d chris2023 -t -c "CREATE DATABASE betty01"

Le message est tout à fait normal, nous sommes dans un contexte de réplication et donc en mode « Lecture »

Liste des bases sur les nodes de réplication (READ)

[root@node-csql ~]# psql -U chris -h node-sql -p 5001 -d chris2023 -t -c "\l"

Liste des utilisateurs sur les nodes de réplication (READ)

[root@node-csql ~]# psql -U chris -h node-sql -p 5001 -d chris2023 -t -c "\du"

Views: 1

L’article MODOP – Partie 4 – PostgreSQL HA – Connexion sql via client Linux est apparu en premier sur CoffeeBreak Info.

• hostmachine : Node-gpsql
  • IP : 192.168.1.113/24
  • OS : Rocky Linux 8.5
  • RAM : 2Go
  • CPU : 1

2. Mise à jour

[root@node-gpsql ~]# dnf update -y

3. Ajout des hosts PosgreSQL

[root@node-gpsql ~]# echo "192.168.1.103 node-psql01" >> /etc/hosts
[root@node-gpsql ~]# echo "192.168.1.104 node-psql02" >> /etc/hosts
[root@node-gpsql ~]# echo "192.168.1.104 node-psql03" >> /etc/hosts
[root@node-gpsql ~]# echo "192.168.1.113 node-pgsql" >> /etc/hosts

4. Désactiver SELinux

[root@node-gpsql ~]# setenforce 0
[root@node-gpsql ~]# sed -i 's/SELINUX=enforcing/SELINUX=disabled/g' /etc/selinux/config

5. Synchroniser DateTime sur le fuseau de PARIS

[root@node-gpsql ~]# timedatectl set-timezone Europe/Paris

6. Installation Grafana

Installation repository

[root@node-gpsql ~]# vi /etc/yum.repos.d/grafana.repo

[grafana]
name=grafana
baseurl=https://packages.grafana.com/oss/rpm
repo_gpgcheck=1
enabled=1
gpgcheck=1
gpgkey=https://packages.grafana.com/gpg.key
sslverify=1
sslcacert=/etc/pki/tls/certs/ca-bundle.crt

[root@node-gpsql ~]# dnf update -y

Installation grafana

[root@node-gpsql ~]# dnf install grafana -y

Start les service grafana

[root@node-gpsql ~]# systemctl start grafana-server
[root@node-gpsql ~]# systemctl enable grafana-server
[root@node-gpsql ~]# systemctl status grafana-server

Règle Firewall

[root@node-gpsql ~]# firewall-cmd --add-port=3000/tcp --permanent && firewall-cmd --reload

Accès Grafana

• http://IP_grafana:3000

• login : admin
• password : admin

7. Installation prometheus

Création user

[root@node-gpsql ~]# adduser -M -r -s /sbin/nologin prometheus

Création structure

[root@node-gpsql ~]# mkdir /etc/prometheus
[root@node-gpsql ~]# mkdir /var/lib/prometheus

[root@node-gpsql ~]# chown prometheus:prometheus /etc/prometheus
[root@node-gpsql ~]# chown prometheus:prometheus /var/lib/prometheus

Récupération des sources

• https://github.com/prometheus/prometheus/releases/

[root@node-gpsql ~]# cd /tmp
[root@node-gpsql tmp]# dnf install wget tar -y

[root@node-gpsql tmp]# wget https://github.com/prometheus/prometheus/releases/download/v2.42.0/prometheus-2.42.0.linux-amd64.tar.gz
[root@node-gsql tmp]# tar xzvf prometheus-2.42.0.linux-amd64.tar.gz

Copier les binaires sur la structure Prometheus

[root@node-gpsql tmp]# cp prometheus-2.42.0.linux-amd64/prometheus /usr/local/bin/
[root@node-gsql tmp]# cp prometheus-2.42.0.linux-amd64/promtool /usr/local/bin/

[root@node-gpsql tmp]# chown prometheus:prometheus /usr/local/bin/prometheus
[root@node-gsql tmp]# chown prometheus:prometheus /usr/local/bin/promtool

Copier les fichiers conf sur la structure Prometheus

[root@node-gpsql tmp]# cp -r prometheus-2.42.0.linux-amd64/consoles /etc/prometheus
[root@node-gpsql tmp]# cp -r prometheus-2.42.0.linux-amd64/console_libraries /etc/prometheus

[root@node-gpsql tmp]# chown -R prometheus:prometheus /etc/prometheus/consoles
[root@node-gpsql tmp]# chown -R prometheus:prometheus /etc/prometheus/console_libraries

Création du service Prometheus

[root@node-gsql tmp]# vi /etc/systemd/system/prometheus.service

[Unit]
Description=Prometheus
Wants=network-online.target
After=network-online.target

[Service]
User=prometheus
Group=prometheus 
Type=simple
ExecStart=/usr/local/bin/prometheus \
--config.file /etc/prometheus/prometheus.yml \
--storage.tsdb.path /var/lib/prometheus/ \
--web.console.templates=/etc/prometheus/consoles \
--web.console.libraries=/etc/prometheus/console_libraries

[Install]
WantedBy=multi-user.target

[root@node-gsql tmp]# systemctl daemon-reload

8. Installation exporter PostgreSQL (Sur les nodes postgreSQL)

Installation prérequis (3 nœuds postgreSQL)

[root@node-psql0x ~]# yum -y install wget tar curl git

Récupération exporter postgreSQL (3 nœuds postgreSQL)

• https://github.com/prometheus-community/postgres_exporter

[root@node-psql0x ~]# cd /home
[root@node-psql0x home]# git clone https://github.com/prometheus-community/postgres_exporter.git

Installation exporter postgreSQL (3 nœuds postgreSQL)

Installation go

• https://go.dev/dl/

[root@node-psql0x home]# wget https://go.dev/dl/go1.20.2.linux-amd64.tar.gz
[root@node-psql0x home]# tar -zxvf go1.20.2.linux-amd64.tar.gz -C /usr/local/

[root@node-psql0x home]# echo 'export GOROOT=/usr/local/go' | sudo tee -a /etc/profile
export GOROOT=/usr/local/go

[root@node-psql0x home]# echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee -a /etc/profile
export PATH=$PATH:/usr/local/go/bin

[root@node-psql0x home]# source /etc/profile

[root@node-psql0x home]# go version
go version go1.20.2 linux/amd64

Compiler « postgres_esporter »

[root@node-psql0x home]# cd postgres_exporter/
[root@node-psql0x postgres_exporter]# make build

Copier le binaire « postgres_esporter » sur /usr/local/bin

[root@node-psql0x postgres_exporter]# ls -al |grep postgres_exporter

[root@node-psql0x postgres_exporter]# cp postgres_exporter /usr/local/bin

Configurer exporter postgreSQL (3 nœuds postgreSQL)

• User : chris
• Password : chris2023
• Dbase : chris2023

[root@node-psql0x postgres_exporter]# vi postgres_exporter.env
DATA_SOURCE_NAME="postgresql://chris:chris2023@localhost:5432/chris2023?sslmode=disable"

Configurer le service exporter postgreSQL (3 nœuds postgreSQL)

Création utilisateur et droits postgres_exporter

[root@node-psql0x postgres_exporter]# adduser -M -r -s /sbin/nologin postgres_exporter
[root@node-psql0x postgres_exporter]# chown -R postgres_exporter:postgres_exporter /home/postgres_exporter

Création du service exporter

[root@node-psql01 postgres_exporter]# vi /etc/systemd/system/postgres_exporter.service

[Unit]
Description=Prometheus exporter for Postgresql
Wants=network-online.target
After=network-online.target

[Service]
User=postgres_exporter
Group=postgres_exporter
WorkingDirectory=/home/postgres_exporter
EnvironmentFile=/home/postgres_exporter/postgres_exporter.env
ExecStart=/usr/local/bin/postgres_exporter --web.listen-address=node-psql0x:9187 --web.telemetry-path=/metrics
Restart=always

[Install]
WantedBy=multi-user.target

Démarrage du service exporter

[root@node-psql0x postgres_exporter]# systemctl daemon-reload
[root@node-psql0x postgres_exporter]# systemctl start postgres_exporter && systemctl enable postgres_exporter

[root@node-psql01 postgres_exporter]# systemctl status postgres_exporter

[root@node-psql01 postgres_exporter]# netstat -antp |grep 9187

Ouverture port firewall pour l’exporter

[root@node-psql01 postgres_exporter]# firewall-cmd --add-port=9187/tcp --permanent && firewall-cmd --reload

Check connexion aux metrics postgreSQL

• http://IP_node-psqlx:9187/metrics

9. Configurer prometheus ⬄ Cluster postgreSQL

[root@node-gpsql tmp]#vi /etc/prometheus/prometheus.yml

global:
scrape_interval: 10s
scrape_configs:
- job_name: postgreSQL
scrape_interval: 5s
static_configs:
- targets: ['node-psql01:9187']
- targets: ['node-psql02:9187']
- targets: ['node-psql03:9187']

[root@node-gpsql tmp]# promtool check config /etc/prometheus/prometheus.yml

Démarrage du service Promotheus

[root@node-gpsql tmp]# systemctl start prometheus && systemctl enable prometheus

[root@node-gpsql tmp]# systemctl status prometheus

Régle firewall

[root@node-gpsql ~]# firewall-cmd --zone=public --add-port=9090/tcp --permanent
[root@node-gpsql ~]# firewall-cmd --reload

Connexion au service Prometheus

• http://IP_Prometheus:9090

« Status » puis « Targets »

Le Cluster postgreSQL est bien présent et « Up » sur Promotheus.

10. Interfacer prometheus / Grafana

• http://IP_grafana:3000

« DATA SOURCES »

Choisir «  Prometheus»

Dans URL préciser l’adresse http de la base Prometheus.

Ajouter un dashboard

« DASHBOARD » puis « + Import »

https://grafana.com/grafana/dashboards/?search=postgres

• ID : 9628
• ID : 455
• ID : 3742
• ID : 4164

« Ajouter l’ID souhaité » puis « Load »

« Import »

Générer du trafic SQL/PostgreSQL

Prérequis

[root@node-gsql ~]# dnf -y install postgresql python3-psycopg2 python3

[root@node-gsql ~]# cd /home
[root@node-gsql home]# echo "192.168.1.110 node-sql" >> /etc/hosts

Récupération du script

[root@node-gsql home]# curl -LO https://raw.githubusercontent.com/jobinau/pgscripts/main/patroni/HAtester.py

[root@node-gsql home]# chmod -x HAtester.py

Configuration du script

[root@node-gsql home]# vi HAtester.py

# CONNECTION DETAILS
host = "node-sql"
dbname = "chris2023"
user = "chris"
password = "chris2023"

Prérequis du script

[root@node-gsql home]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "CREATE TABLE HATEST (TM TIMESTAMP);"

[root@node-gsql home]# psql -U chris -h node-sql -p 5000 -d chris2023 -t -c "CREATE UNIQUE INDEX idx_hatext ON hatest (tm desc);"

Générer trafic « MASTER »

[root@node-gpsql home]# ./HAtester.py 5000

Générer trafic « REPLICA »

[root@node-gsql home]# ./HAtester.py 5001

Monitoring Grafana – Cluster postgreSQL

Check des hosts monitorés

Check des bases monitorées

Sur 1 heures

Node-sql01

Node-sql02

Node-sql03

Node-sql01

Node-sql02

Node-sql02

Sur 12heures

Node-psql01

Node-psql02

Node-psql03

Views: 3

L’article MODOP – Partie 6 – PostgreSQL HA – Grafana/Prometheus : Cluster PostgreSQL est apparu en premier sur CoffeeBreak Info.

• Serveur sql01.house.cpb  IP 192.168.1.62
• Serveur sql02.house.cpb  IP 192.168.1.63

Dans le DNS :

• sql.house.cpb. IN A 192.168.1.62
• sql.house.cpb. IN A 192.168.1.63

1° ) Installation Base de données/PhpMyadmin (ql01.house.cpb/sql02.house.cpb)

root@sql01:/home/sysbreak# apt-get install mysql-server mysql-client
root@sql01:/home/sysbreak# systemctl enable mariadb.service
root@sql01:/home/sysbreak# systemctl start mariadb.service

Configuration

root@sql01:/home/sysbreak# mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MariaDB
SERVERS IN PRODUCTION USE! PLEASE READ EACH STEP CAREFULLY!
In order to log into MariaDB to secure it, we'll need the current
password for the root user. If you've just installed MariaDB, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.

Enter current password for root (enter for none): « ENTER »
OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MariaDB
root user without the proper authorisation.
Set root password? [Y/n] yes
New password:
Re-enter new password:
Password updated successfully!
Reloading privilege tables..
... Success!

By default, a MariaDB installation has an anonymous user, allowing anyone
to log into MariaDB without having to have a user account created for
them. This is intended only for testing, and to make the installation
go a bit smoother. You should remove them before moving into a
production environment.
Remove anonymous users? [Y/n] y
... Success!

Normally, root should only be allowed to connect from 'localhost'. This
ensures that someone cannot guess at the root password from the network.
Disallow root login remotely? [Y/n] n
... skipping.

By default, MariaDB comes with a database named 'test' that anyone can
access. This is also intended only for testing, and should be removed
before moving into a production environment.
Remove test database and access to it? [Y/n] n
... skipping.

Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
Reload privilege tables now? [Y/n] y
... Success!
Cleaning up...

All done! If you've completed all of the above steps, your MariaDB
installation should now be secure.
Thanks for using MariaDB!

Installer PhpMyAdmin

root@sql01:/etc# apt install phpmyadmin

« apache2 »

« oui »

« Taper un mot de passe »

« Confirmer le mot de passe »

Régler le Souci suivant :

root@sql01:/etc/apache2# mysql --user=root mysql
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 16
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [mysql]> use mysql;
Database changed
MariaDB [mysql]> update user set plugin='' where User='root';
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

MariaDB [mysql]> flush privileges;
Query OK, 0 rows affected (0.00 sec)

MariaDB [mysql]> exit;

2°) Modifier les Fichier Systèmes my.cnf pour les Deux Servers SQL01 et SQL02

Pour le Serveur SQL01

chris@sql01:/etc/mysql$ vi my.cnf
Ajouter les Lignes Suivantes
[mysqld]
server_id = 1
log_bin = /var/log/mysql/mysql-bin.log
log_bin_index = /var/log/mysql/mysql-bin.log.index
relay_log = /var/log/mysql/mysql-relay-bin
relay_log_index = /var/log/mysql/mysql-relay-bin.index
expire_logs_days = 10
max_binlog_size = 100M
log_slave_updates = 1
auto-increment-increment = 2
auto-increment-offset = 1

éditer le fichier 50-server.conf

chris@sql01:/etc/mysql$ vi ./mariadb.conf.d/50-server.cnf
Modifier la bind-address
bind-address = 192.168.1.62 (Adresse du Serveur SQL01)

Redémarrer le serveur de base de données.

Pour le Serveur SQL02

chris@sql02:/etc/mysql$ vi my.cnf

#Ajouter les Lignes Suivantes
[mysqld]
server_id = 2
log_bin = /var/log/mysql/mysql-bin.log
log_bin_index = /var/log/mysql/mysql-bin.log.index
relay_log = /var/log/mysql/mysql-relay-bin
relay_log_index = /var/log/mysql/mysql-relay-bin.index
expire_logs_days = 10
max_binlog_size = 100M
log_slave_updates = 1
auto-increment-increment = 2
auto-increment-offset = 2

éditer le fichier 50-server.conf

chris@sql02:/etc/mysql$ vi ./mariadb.conf.d/50-server.cnf
Modifier la bind-address
bind-address = 192.168.1.63 (Adresse du Serveur SQL02)

Redémarrer le serveur de base de données.
Vérifier que les deux server SQL01 et SQL02 écoute sur leurs adresses IP et non Localhost

3°) Création du compte ‘replication’ pour la réplication (à faire sur les deux bases)

Sur Sql01

On va créer un compte user ‘replication’ avec l’IP de SQL02 (192.168.1.63)
GRANT REPLICATION SLAVE ON *.* TO ‘replication’@’192.168.1.63’ IDENTIFIED BY ‘replication@2019’;

root@sql01:/etc# mysql -u root –p
Enter password: « PASWORD »

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 7
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> GRANT REPLICATION SLAVE ON *.* TO 'replication'@'192.168.1.63' IDENTIFIED BY 'replication@2019';
Query OK, 0 rows affected (0.00 sec)

Sur Sql02

On va créer un compte user ‘replication’ avec l’IP de SQL01 (192.168.1.62)
GRANT REPLICATION SLAVE ON *.* TO ‘replication’@’192.168.1.62’ IDENTIFIED BY ‘replication@2019’;

root@sql01:/etc# mysql -u root –p
Enter password: « PASWORD »

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 7
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> GRANT REPLICATION SLAVE ON *.* TO 'replication'@'192.168.1.62' IDENTIFIED BY 'replication@2019';
Query OK, 0 rows affected (0.00 sec)

Faire un test Croisé sur les deux bases afin de vérifier que les deux bases puissent se connecter entre elles via le compte ‘replication’

Ex : on est sur sql02 et on se connecte sur ma base SQL01 avec le compte ‘replication’*’192.168.1 .62’

4°) Réaliser la Réplication Master – Master entre les Deux bases

MASTER SQL02

Sur SQL01 Récupérer le Status MASTER

root@sql01:/etc/mysql# mysql -u root -p
Enter password: « PASWORD »
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> SHOW MASTER STATUS;
+------------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000004 | 1045 | | |
+------------------+----------+--------------+------------------+
1 row in set (0.00 sec)
MariaDB [(none)]>

Sur SQL02 intégrer le status MASTER SQL01
A passer dans la requête sur SQL02 ci-dessous

• Mot de passe réplication de SQLO1
• IP de SQL01
• Master_log_file de SQL01 (ci-dessus)
• Master_log_pos de SQL01 (ci-dessus)

root@sql02:/etc/mysql/mariadb.conf.d# mysql -u root -p
Enter password: « PASWORD »

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 36
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> STOP SLAVE;
Query OK, 0 rows affected, 1 warning (0.00 sec)

MariaDB [(none)]> CHANGE MASTER TO master_host='192.168.1.62' , master_port=3306, master_user='replication' , master_password='replication@2019',master_log_file='mysql-bin.000004',master_log_pos=1045;
Query OK, 0 rows affected (0.05 sec)

MariaDB [(none)]> START SLAVE;
Query OK, 0 rows affected (0.00 sec)

MASTER SQL01
Sur SQL02 Récupérer le Status MASTER

root@sql02:/etc/mysql# mysql -u root -p
Enter password:

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 17
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> SHOW MASTER STATUS;
+------------------+----------+--------------+------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
+------------------+----------+--------------+------------------+
| mysql-bin.000002 | 1045 | | |
+------------------+----------+--------------+------------------+

A passer dans la requête sur SQL01 ci-dessous1 row in set (0.00 sec)
MariaDB [(none)]>
Sur SQL01 intégrer le status MASTER SQL02

• Mot de passe réplication de SQL02
• IP de SQL02
• Master_log_file de SQL02 (ci-dessus)
• Master_log_pos de SQL02 (ci-dessus)

root@sql01:/etc/mysql/mariadb.conf.d# mysql -u root -p
Enter password:« PASWORD »

Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 36
Server version: 10.1.38-MariaDB-0+deb9u1 Debian 9.8
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> STOP SLAVE;
Query OK, 0 rows affected, 1 warning (0.00 sec)

MariaDB [(none)]> CHANGE MASTER TO master_host='192.168.1.63' , master_port=3306, master_user='replication' , master_password='replication@2019',master_log_file='mysql-bin.000002',master_log_pos=1045;
Query OK, 0 rows affected (0.05 sec)

MariaDB [(none)]> START SLAVE;
Query OK, 0 rows affected (0.00 sec)

5°) Test de la Réplication – Création BASE et TABLE

Créer une Table sur SQL01 cela devrait créer la même table sur SQL02

Sur SQL01

MariaDB [(none)]> create database chris;
Query OK, 1 row affected (0.00 sec)

MariaDB [(none)]> create table chris.flowers (`id` varchar(10));
Query OK, 0 rows affected (0.02 sec)

Sur SQL02

MariaDB [(none)]> show tables in chris;
+-----------------+
| Tables_in_chris |
+-----------------+
| flowers |
+-----------------+
1 row in set (0.00 sec)

La table se retrouve à présent aussi sur SQL02.

6°) Test suppession TABLE – Création BASE et TABLE

Supprimer la table ‘chris.flowers’ sur SQL02 er vérifions la suppression sur SQL01.

Sur SQL02

MariaDB [(none)]> drop table chris.flowers;
Query OK, 0 rows affected (0.01 sec)

Sur SQL01
MariaDB [(none)]> show tables in chris;
Empty set (0.00 sec)

La table « chris » est vide donc la réplication fonctionne.

7°) Affichage dans PhpMyAdmin

Affichage PhpMyadmin SQL01

Affichage PhpMyadmin SQL02

Views: 12

L’article MODOP – Réplication MASTER – MASTER entre Deux bases Mysql est apparu en premier sur CoffeeBreak Info.