How to configure high-availability database cluster monitoring on Linux

How to configure high-availability database cluster monitoring on Linux

Introduction:
In modern enterprise systems, the database is a crucial component. In order to ensure the high availability and continuous stable operation of the database, configuring high-availability database cluster monitoring on Linux is a necessary step. This article will introduce how to configure high-availability database cluster monitoring in a Linux environment and provide relevant code examples.

1. Install and configure database cluster
Before configuring database cluster monitoring, you first need to build a reliable database cluster. Taking the MySQL database as an example, the following are the steps to install and configure the MySQL database cluster:

1. Download and install the MySQL database
   Execute the following command on each node to install:

   $ sudo apt-get update
   $ sudo apt-get install mysql-server

2. Configuring the MySQL database master node
   Open the MySQL configuration file of the master node (usually in /etc/mysql/my.cnf) and perform the following configuration:

   [mysqld]
   server-id=1
   log-bin=mysql-bin
   binlog-format=ROW

3. Configuring the MySQL database slave node
   Open the MySQL configuration file of the slave node and perform the following configuration:

   [mysqld]
   server-id=2
   relay-log=mysql-relay-bin
   log-bin=mysql-bin
   binlog-format=ROW
   read-only=1

4. Start the database
   On each node Execute the command to start the database server:

   $ sudo systemctl start mysql

2. Use Keepalived to achieve high availability
Keepalived is an open source tool that can be used to achieve high availability of services. The following are the steps to configure database cluster high availability using Keepalived:

1. Install Keepalived
   Execute the following command on each node to install:

   $ sudo apt-get install keepalived

2. Configuring Keepalived
   Open the Keepalived configuration file (usually in /etc/keepalived/keepalived.conf) and configure the following:

   vrrp_script check_mysql {
       script "/usr/bin/mysqladmin ping"
       interval 2
       weight -1
       fall 3
       rise 2
   }
   
   vrrp_instance VI_1 {
       interface eth0
       state BACKUP
       virtual_router_id 51
       priority 100
       advert_int 1
       authentication {
           auth_type PASS
           auth_pass strongpassword
       }
       virtual_ipaddress {
           192.168.1.100
       }
       track_script {
           check_mysql
       }
   }

3. Start Keepalived
   In each Execute the following command on the node to start the Keepalived service:

   $ sudo systemctl start keepalived

3. Use Pacemaker and Corosync to implement cluster monitoring
Pacemaker is a tool for cluster management and automatic failover, while Corosync It is software used to implement cluster communication. The following are the steps to configure database cluster monitoring using Pacemaker and Corosync:

1. Install Pacemaker and Corosync
   Execute the following command on each node to install:

   $ sudo apt-get install pacemaker corosync

2. Configure Corosync
   Open the Corosync configuration file (usually in /etc/corosync/corosync.conf) and configure the following:

   totem {
       version: 2
       secauth: on
       cluster_name: my_cluster
       transport: udpu
   }
   
   nodelist {
       node {
           ring0_addr: node1_ip
           name: node1
           nodeid: 1
       }
       node {
           ring0_addr: node2_ip
           name: node2
           nodeid: 2
       }
       /* Add more nodes as necessary */
   }
   
   quorum {
       provider: corosync_votequorum
   }

3. Configure Pacemaker
   Execute the following command on each node to configure Pacemaker:

   $ sudo crm configure
   crm(live)> property no-quorum-policy=ignore
   crm(live)> rsc_defaults resource-stickiness=100
   crm(live)> rsc_defaults migration-threshold=1
   crm(live)> configure primitive mysql lsb:mysql op monitor interval=30s
   crm(live)> configure clone mysql-clone mysql meta clone-max=2 clone-node-max=1
   crm(live)> configure group mysql-group mysql-clone
   crm(live)> verify
   crm(live)> commit

Conclusion:
Through the above configuration, we successfully implemented high-availability database cluster monitoring on Linux. In this way, our database system can continue to run even in the event of node failure, ensuring system stability and availability.

Reference code example:

1. MySQL master node configuration file example (/etc/mysql/my.cnf):

   [mysqld]
   server-id=1
   log-bin=mysql-bin
   binlog-format=ROW

2. MySQL slave node configuration file example (/etc/mysql/my.cnf):

   [mysqld]
   server-id=2
   relay-log=mysql-relay-bin
   log-bin=mysql-bin
   binlog-format=ROW
   read-only=1

3. Keepalived configuration file example (/etc/keepalived/keepalived.conf):

   vrrp_script check_mysql {
   script "/usr/bin/mysqladmin ping"
   interval 2
   weight -1
   fall 3
   rise 2
   }
   
   vrrp_instance VI_1 {
   interface eth0
   state BACKUP
   virtual_router_id 51
   priority 100
   advert_int 1
   authentication {
       auth_type PASS
       auth_pass strongpassword
   }
   virtual_ipaddress {
       192.168.1.100
   }
   track_script {
       check_mysql
   }
   }

4. Pacemaker configuration command example:

   $ sudo crm configure
   crm(live)> property no-quorum-policy=ignore
   crm(live)> rsc_defaults resource-stickiness=100
   crm(live)> rsc_defaults migration-threshold=1
   crm(live)> configure primitive mysql lsb:mysql op monitor interval=30s
   crm(live)> configure clone mysql-clone mysql meta clone-max=2 clone-node-max=1
   crm(live)> configure group mysql-group mysql-clone
   crm(live)> verify
   crm(live)> commit

The above is the detailed content of How to configure high-availability database cluster monitoring on Linux. For more information, please follow other related articles on the PHP Chinese website!