目錄

一、MHA概述

1、簡介

2、MHA特點(diǎn)

3、何為高可用

4、故障切換過程

二、MHA高可用架構(gòu)部署

1、架構(gòu)圖

2、?實(shí)驗(yàn)環(huán)境：需要四臺Centos7服務(wù)器

3、實(shí)驗(yàn)部署

3.1、master、slave1、slave2安裝mysql服務(wù)，之前博客有編譯安裝教程

3.2、master、slave1、slave2上配置my.cnf

3.3、在master、slave1、slave2上分別做兩個軟鏈接

3.4、重啟3臺MySQL服務(wù)，再查看端口，是否啟動成功

3.5、配置主從復(fù)制

3.6、在manager主機(jī)上配置mha

3.7、配置無密碼認(rèn)證

3.8、在manager節(jié)點(diǎn)上配置MHA腳本

3.9、創(chuàng)建 MHA 軟件目錄并拷貝配置文件

三、測試

1、在manager端測試無密碼認(rèn)證

2、測試主從復(fù)制

3、啟動mha

4、查看到當(dāng)前的master節(jié)點(diǎn)

5、查看當(dāng)前日志信息

6、模擬master宕機(jī)，slave1是否能頂上

?

一、MHA概述

1、簡介

MHA（Master High Availability）目前在MySQL高可用方面是一個相對成熟的解決方案，MHA是由
日本人開發(fā)，是一套優(yōu)秀的MySQL故障切換和主從復(fù)制的高可用軟件。

在MySQL故障切換的過程中，MHA能做到0~30秒之內(nèi)自動完成數(shù)據(jù)庫的故障切換操作，并且在進(jìn)行故障切換的過程中，MHA能夠最大程度上保證數(shù)據(jù)庫的一致性，以達(dá)到真正意義上的高可用。

MHA里有 兩個角色一個是MHA Node（數(shù)據(jù)節(jié)點(diǎn)）另一個是MHA Manager（管理節(jié)點(diǎn)）。MHA Manager可以單獨(dú)部署 在一臺獨(dú)立的機(jī)器上管理多個master-slave集群，也可以部署在一臺slave節(jié)點(diǎn)上。MHA Node運(yùn)行在每臺 MySQL服務(wù)器上，MHA Manager會定時探測集群中的master節(jié)點(diǎn)，當(dāng)master出現(xiàn)故障時，它可以自動將最新 數(shù)據(jù)的slave提升為新的master，然后將所有其他的slave重新指向新的master。整個故障轉(zhuǎn)移過程對應(yīng)用程序完全透明。

2、MHA特點(diǎn)

自動故障切換過程中，MHA總會試圖從宕機(jī)的主服務(wù)器上保存二進(jìn)制日志，最大程度的保證數(shù)據(jù)不丟失。

但這并不總是可行，例如如果主服務(wù)器硬件故障或者無法通過ssh訪問，MHA則無法保存二進(jìn)制日志，只能進(jìn)行故障轉(zhuǎn)移而丟失了最新的數(shù)據(jù)。此時，使用MySQL5.5的半同步復(fù)制，可以大大降低數(shù)據(jù)丟失的風(fēng)險。MHA可以與半同步復(fù)制結(jié)合起來，如果只有一個slave已經(jīng)收到了最新的二進(jìn)制日志，MHA可以將最新的二進(jìn)制日志應(yīng)用于其他所有的slave服務(wù)器上，因此可以保證所有節(jié)點(diǎn)的數(shù)據(jù)一致性，有時候可故意設(shè)置從節(jié)點(diǎn)慢于主節(jié)點(diǎn)，當(dāng)發(fā)生意外刪除數(shù)據(jù)庫倒是數(shù)據(jù)丟失時可從從節(jié)點(diǎn)二進(jìn)制日志中恢復(fù)。

3、何為高可用

高可用就是可用性強(qiáng)，在一定條件下（某個服務(wù)器出錯或宕機(jī)）可以保證服務(wù)器可以正常運(yùn)行，在一定程度上不會影響業(yè)務(wù)的運(yùn)行。

4、故障切換過程

當(dāng)主服務(wù)器出現(xiàn)錯誤時，被manager服務(wù)器監(jiān)控到主庫mysqld服務(wù)停止后，首先對主庫進(jìn)行SSH登錄檢查（save_binary_logs -command=test），然后對mysqld服務(wù)進(jìn)行健康檢查（PING(SELECT)每個3秒檢查一次，持續(xù)3次），最后作出Master is down!的判斷，master failover開始進(jìn)行對應(yīng)的處理

二、MHA高可用架構(gòu)部署

安裝包下載：

https://download.csdn.net/download/m0_62948770/86724795

1、架構(gòu)圖

2、?實(shí)驗(yàn)環(huán)境：需要四臺Centos7服務(wù)器

①一臺作為mha服務(wù)器（manager）來監(jiān)控管理下面的MySQL服務(wù)器

②三臺:一主兩從MySQL服務(wù)器

實(shí)驗(yàn)流程：

安裝編譯環(huán)境——> 安裝MySQL5.6.36數(shù)據(jù)庫——>配置時間同步——>配置主從復(fù)制與儲備MySQL服務(wù)器——>安裝node工具——>配置mha服務(wù)器——>測試驗(yàn)證

3、實(shí)驗(yàn)部署

3.1、master、slave1、slave2安裝mysql服務(wù)，之前博客有編譯安裝教程

3.2、master、slave1、slave2上配置my.cnf

修改master的配置文件my.cnf

[root@master ~]# vim /etc/my.cnf

[client]
port = 3306
#default-character-set=utf8                    ## 注銷字符集
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
#default-character-set=utf8                   ## 注銷字符集
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
#character_set_server=utf8                    ## 注銷字符集
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 1                          

##增加內(nèi)容
log_bin = master-bin                   
log-slave-update = true                

修改slave1的配置文件my.cnf

[root@slave1 ~]# vim /etc/my.cnf
[client]
port = 3306
#default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
#default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
#character_set_server=utf8
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock

server-id =2                               ## 修改為2 
log_bin = master-bin                       ## 開啟二進(jìn)制日志                    
relay-log = relay-log-bin                  ## 使用中繼日志進(jìn)行同步       
relay-log-index = slave-relay-bin.index    ## 索引

修改slave2的配置文件my.cnf

[root@zew_slave2 ~]# vim /etc/my.cnf

[client]
[mysql]
port = 3306
#default-character-set=utf8
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
#character_set_server=utf8
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 3
log_bin = master-bin
relay-log = relay-log-bin
relay-log-index = slave-relay-bin.index

3.3、在master、slave1、slave2上分別做兩個軟鏈接

############ 只做master上的配置演示了 ###########################

[root@master ~]# ln -s /usr/local/mysql/bin/mysql /usr/sbin
[root@master ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin

3.4、重啟3臺MySQL服務(wù)，再查看端口，是否啟動成功

[root@master ~]# systemctl restart mysqld.service? ? ?## 只演示master節(jié)點(diǎn)了

[root@master ~]# netstat -natp | grep 3306
tcp6 ? ? ? 0 ? ? ?0 :::3306 ? ? ? ? ? ? ? ? :::* ? ? ? ? ? ? ? ? ? ?LISTEN ? ? ?10503/mysqld?

3.5、配置主從復(fù)制

在所有數(shù)據(jù)庫節(jié)點(diǎn)上授權(quán)兩個用戶，一個是從數(shù)據(jù)庫同步使用用戶myslave，另一個是manager 使用用戶mha

grant replication slave on *.* to 'myslave'@'192.168.159.%' identified by '123456';?
grant all privileges on *.* to 'mha'@'192.168.159.%' identified by 'manager';

下面三條授權(quán)理論上不用添加，但是實(shí)驗(yàn)環(huán)境通過MHA檢查MySQL主從報錯，報兩個從庫通過主機(jī)名連接不上主庫，所以所有數(shù)據(jù)庫都需要添加以下授權(quán)，通過mha檢查的時候，是通過主機(jī)名的形式進(jìn)行監(jiān)控，這種情況會容易報錯。

grant all privileges on *.* to 'mha'@'master' identified by 'manager';
grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';

把從庫均設(shè)為只讀功能：set global read_only=1;

master

[root@master ~]# mysql -uroot -pabc123


mysql> grant replication slave on *.* to 'myslave'@'192.168.159.%' identified by '123456';
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> grant all privileges on *.* to 'mha'@'192.168.159.%' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)


mysql> grant all privileges on *.* to 'mha'@'master' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

slave1

[root@master ~]# mysql -uroot -pabc123


mysql> grant replication slave on *.* to 'myslave'@'192.168.159.%' identified by '123456'; 
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'192.168.159.%' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'master' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)


#### 所有從庫開啟只讀功能（不會對超級管理員super生效，普通用戶）
mysql> set global read_only=1;
Query OK, 0 rows affected (0.00 sec)

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

slave2

[root@slave2 ~]# mysql -uroot -pabc123


mysql> grant replication slave on *.* to 'myslave'@'192.168.159.%' identified by '123456';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'192.168.159.%' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'master' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';
Query OK, 0 rows affected, 1 warning (0.00 sec)



### 所有從庫開啟只讀功能（不會對超級管理員super生效，普通用戶）
mysql> set global read_only=1;
Query OK, 0 rows affected (0.00 sec)

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

同步

在master上查看二進(jìn)制文件和同步點(diǎn)

mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 |     1595 |              |                  |                   |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

在slave1數(shù)據(jù)庫中配置

mysql> change master to master_host='192.168.159.68',master_user='myslave',master_password='123456',master_log_file='master-bin.000001',master_log_pos=1595;
Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.159.68
                  Master_User: myslave
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: master-bin.000001
          Read_Master_Log_Pos: 1595
               Relay_Log_File: relay-log-bin.000002
                Relay_Log_Pos: 321
        Relay_Master_Log_File: master-bin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 1595
              Relay_Log_Space: 526
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
............................................

在slave2上數(shù)據(jù)庫中配置

mysql> change master to master_host='192.168.159.68',master_user='myslave',master_password='123456',master_log_file='master-bin.000001',master_log_pos=1595;
Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;
Query OK, 0 rows affected (0.00 sec)

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Connecting to master
                  Master_Host: 192.168.159.68
                  Master_User: myslave
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: master-bin.000001
          Read_Master_Log_Pos: 1595
               Relay_Log_File: relay-log-bin.000001
                Relay_Log_Pos: 4
        Relay_Master_Log_File: master-bin.000001
             Slave_IO_Running: Connecting
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 1595
              Relay_Log_Space: 154
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: NULL
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
.............................................

3.6、在manager主機(jī)上配置mha

安裝MHA依賴的環(huán)境及安裝epel源（每臺節(jié)點(diǎn)都需要安裝這依賴環(huán)境，因?yàn)槊颗_都要安裝node）

yum install epel-release --nogpgcheck -y?

yum install -y perl-DBD-MySQL \?

perl-Config-Tiny \
perl-Log-Dispatch \
perl-Parallel-ForkManager \
perl-ExtUtils-CBuilder \
perl-ExtUtils-MakeMaker \
perl-CPAN

安裝node(四臺節(jié)點(diǎn)都需要安裝，方法一樣)

[root@manager ~]# cd /opt

[root@manager opt]# rz -E             ## 上傳安裝包到opt下
rz waiting to receive.
[root@manager opt]# ls
mha4mysql-manager-0.57.tar.gz  rh
mha4mysql-node-0.57.tar.gz

[root@manager opt]# tar zxf mha4mysql-node-0.57.tar.gz
[root@manager opt]# cd mha4mysql-node-0.57/
[root@manager mha4mysql-node-0.57]# perl Makefile.PL



[root@manager mha4mysql-node-0.57]# make && make install

安裝manager組件

[root@manager mha4mysql-node-0.57]# cd /opt/
[root@manager opt]# tar -zxvf mha4mysql-manager-0.57.tar.gz

[root@manager opt]# cd mha4mysql-manager-0.57
[root@manager mha4mysql-manager-0.57]# perl Makefile.PL


[root@manager mha4mysql-manager-0.57]# make && make install

manager 安裝后在/usr/local/bin 下面會生成幾個工具，主要包括以下幾個：

masterha_check_ssh? ? ? ? ? ? ? ? ? ## 檢查MHA的SSH的配置狀況
masterha_check_repl? ? ? ? ? ? ? ? ? ## 檢查MySQL復(fù)制狀況
masterha_manager? ? ? ? ? ? ? ? ? ? ?## ?啟動manager腳本
masterha_check_status? ? ? ? ? ? ? ## ?檢查當(dāng)前MHA運(yùn)行狀態(tài)
masterha_master_monitor? ? ? ? ? ## ?檢測master是否宕機(jī)
masterha_master_switch? ? ? ? ? ? ##? 控制故障轉(zhuǎn)移（自動或者手動）
masterha_conf_host? ? ? ? ? ? ? ? ? ?## ?添加或刪除配置的server信息
masterha_stop? ? ? ? ? ? ? ? ? ? ? ? ? ? ## ?關(guān)閉manager

[root@manager mha4mysql-manager-0.57]# cd /usr/local/bin/
[root@manager bin]# ls
apply_diff_relay_logs  masterha_master_monitor
filter_mysqlbinlog     masterha_master_switch
masterha_check_repl    masterha_secondary_check
masterha_check_ssh     masterha_stop
masterha_check_status  purge_relay_logs
masterha_conf_host     save_binary_logs
masterha_manager

四臺節(jié)點(diǎn)在node安裝后都會在/usr/local/bin 下面會生成一下幾個腳本（這些工具通常由MHA manager的腳本觸發(fā)，無需人為操作）主要如下：
save_binary_logs? ? ? ? ? ? ? ? ### 保存和復(fù)制master的二進(jìn)制日志
apply_diff_relay_logs? ? ? ? ? ###? 識別差異的中繼日志事件并將其差異的事件應(yīng)用于其他的slave
filter_mysqlbinlog? ? ? ? ? ? ? ? ###? 去除不必要的ROLLBACK事件（MHA已不再使用這個工具）
purge_relay_logs? ? ? ? ? ? ? ? ###? ?清除中繼日志（不會阻塞SQL線程）

[root@master mha4mysql-node-0.57]# cd /usr/local/bin/
[root@master bin]# ls
apply_diff_relay_logs  filter_mysqlbinlog  purge_relay_logs  save_binary_logs

3.7、配置無密碼認(rèn)證

①在 master 上配置到所有數(shù)據(jù)庫節(jié)點(diǎn)的無密碼認(rèn)證

[root@master ~]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):    ## 回車
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase):                 ## 回車
Enter same passphrase again:                                ## 回車
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:                                     ## 回車
SHA256:TS1zC5lCuQRj/ILwKh8MGqSmcC1jubyE+rnWVg5k8bA root@master
The key's randomart image is:                               ## 回車
+---[RSA 2048]----+
|     .+...       |
| .. o..oo  +     |
|o  = * o..B o    |
|=.* E o o+ = .   |
|=O B   .S . .    |
|= B . .          |
|.+ + +           |
|. +.o .          |
| o+o             |
+----[SHA256]-----+
 
[root@master ~]# ssh-copy-id 192.168.159.11         ## 到slave1的免密登錄
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '192.168.159.11 (192.168.159.11)' can't be established.
ECDSA key fingerprint is SHA256:/foExVQ7yWnkh6o06Me2Naf74YXIhWUC7cZf5cC030k.
ECDSA key fingerprint is MD5:83:dd:28:fc:10:70:e3:9c:bf:f0:26:0a:30:78:10:c2.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@192.168.159.11's password:     ## 虛擬機(jī)登錄密碼

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh '192.168.159.11'"
and check to make sure that only the key(s) you wanted were added.

[root@master ~]# ssh-copy-id 192.168.159.10
...............................................


[root@master ~]# ssh-copy-id 192.168.159.13
...............................................


[root@master ~]# ssh-copy-id 192.168.159.68
...............................................

②在 slave1 上配置到所有數(shù)據(jù)庫節(jié)點(diǎn)的無密碼認(rèn)證

ssh-keygen -t rsa

ssh-copy-id 192.168.159.11
ssh-copy-id 192.168.159.68
ssh-copy-id 192.168.159.10
ssh-copy-id 192.168.226.13

③在 slave2上配置到所有數(shù)據(jù)庫節(jié)點(diǎn)的無密碼認(rèn)證

ssh-keygen -t rsa

ssh-copy-id 192.168.159.10
ssh-copy-id 192.168.159.68
ssh-copy-id 192.168.159.11
ssh-copy-id 192.168.226.13

④在 manager上配置到所有數(shù)據(jù)庫節(jié)點(diǎn)的無密碼認(rèn)證

ssh-keygen -t rsa

ssh-copy-id 192.168.226.13
ssh-copy-id 192.168.159.68
ssh-copy-id 192.168.159.11
ssh-copy-id 192.168.226.10

3.8、在manager節(jié)點(diǎn)上配置MHA腳本

在 manager 節(jié)點(diǎn)上復(fù)制相關(guān)腳本到/usr/local/bin 目錄

[root@manager scripts]# cp -ra /opt/mha4mysql-manager-0.57/samples/scripts/ /usr/local/bin

#-a：此選項通常在復(fù)制目錄時使用，它保留鏈接、文件屬性，并復(fù)制目錄下的所有內(nèi)容
#-r: 遞歸

[root@manager scripts]# ll /usr/local/bin/scripts/
總用量 32
-rwxr-xr-x 1 wangwu wangwu  3648 5月  31 2015 master_ip_failover  #自動切換時 VIP管理 
                                                                      的腳本
-rwxr-xr-x 1 wangwu wangwu  9870 5月  31 2015 master_ip_online_change #在線切換時 VIP 
                                                                        的管理
-rwxr-xr-x 1 wangwu wangwu 11867 5月  31 2015 power_manager #故障發(fā)生后關(guān)閉主機(jī)的腳本
-rwxr-xr-x 1 wangwu wangwu  1360 5月  31 2015 send_report  #因故障切換后發(fā)送報警的腳本 

復(fù)制上述的自動切換時 VIP 管理的腳本到/usr/local/bin 目錄，這里使用腳本管理 VIP

[root@manager scripts]# cd /usr/local/bin/scripts/
[root@manager scripts]# ls
master_ip_failover       power_manager
master_ip_online_change  send_report
[root@manager scripts]# cp master_ip_failover /usr/local/bin/[root@manager scripts]# 

修改配置文件master_ip_failover（刪除原有內(nèi)容，直接復(fù)制）

[root@manager scripts]# pwd
/usr/local/bin/scripts
[root@manager scripts]# vim /usr/local/bin/master_ip_failover

#!/usr/bin/env perl 
use strict;
use warnings FATAL => 'all';

use Getopt::Long;

my (
$command, $ssh_user, $orig_master_host, $orig_master_ip,
$orig_master_port, $new_master_host, $new_master_ip, $new_master_port
);
my $vip = '192.168.159.100';	             ## 設(shè)置vip	
my $brdc = '192.168.159.255';	              ## 設(shè)置廣播地址
my $ifdev = 'ens33';		
my $key = '1';			
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip";		
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down";		
my $exit_code = 0;			
#my $ssh_start_vip = "/usr/sbin/ip addr add $vip/24 brd $brdc dev $ifdev label $ifdev:$key;/usr/sbin/arping -q -A -c 1 -I $ifdev $vip;iptables -F;";
#my $ssh_stop_vip = "/usr/sbin/ip addr del $vip/24 dev $ifdev label $ifdev:$key";
GetOptions(
'command=s' => \$command,
'ssh_user=s' => \$ssh_user,
'orig_master_host=s' => \$orig_master_host,
'orig_master_ip=s' => \$orig_master_ip,
'orig_master_port=i' => \$orig_master_port,
'new_master_host=s' => \$new_master_host,
'new_master_ip=s' => \$new_master_ip,
'new_master_port=i' => \$new_master_port,
);

exit &main();

sub main {

print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";

if ( $command eq "stop" || $command eq "stopssh" ) {

my $exit_code = 1;
eval {
print "Disabling the VIP on old master: $orig_master_host \n";
&stop_vip();
$exit_code = 0;
};
if ($@) {
warn "Got Error: $@\n";
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "start" ) {

my $exit_code = 10;
eval {
print "Enabling the VIP - $vip on the new master - $new_master_host \n";
&start_vip();
$exit_code = 0;
};
if ($@) {
warn $@;
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "status" ) {
print "Checking the Status of the script.. OK \n";
exit 0;
}
else {
&usage();
exit 1;
}
}
sub start_vip() {
`ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
}

sub usage {
print
"Usage: master_ip_failover --command=start|stop|stopssh|status --orig_master_host=host --orig_master_ip=ip --orig_master_port=port --new_master_host=host --new_master_ip=ip --new_master_port=port\n";
}

3.9、創(chuàng)建 MHA 軟件目錄并拷貝配置文件

[root@manager scripts]# pwd
/usr/local/bin/scripts
[root@manager scripts]# mkdir /etc/masterha

[root@manager scripts]# cp /opt/mha4mysql-manager-0.57/samples/conf/app1.cnf /etc/masterha/


[root@manager scripts]# vim /etc/masterha/app1.cnf

[server default]
manager_workdir=/var/log/masterha/app1
manager_log=/var/log/masterha/app1/manager.log

master_binlog_dir=/usr/local/mysql/data/            ## 修改下二進(jìn)制日志的位置
password=manager
ping_interval=1
remote_workdir=/tmp
repl_password=123456
repl_user=myslave
secondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.159.11 -s 192.168.159.10shutdown_script=""
ssh_user=root
user=mha

[server1]
hostname=192.168.159.68
port=3306

[server2]
candidate_master=1
hostname=192.168.226.11
check_repl_delay=0
port=3306

[server3]
hostname=192.168.226.10
port=3306

三、測試

1、在manager端測試無密碼認(rèn)證

[root@manager conf]# masterha_check_ssh -conf=/etc/masterha/app1.cnf
Tue Sep 27 22:58:26 2022 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Sep 27 22:58:26 2022 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Sep 27 22:58:26 2022 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Tue Sep 27 22:58:26 2022 - [info] Starting SSH connection tests..
Tue Sep 27 22:58:28 2022 - [debug] 
Tue Sep 27 22:58:27 2022 - [debug]  Connecting via SSH from root@192.168.159.10(192.168.159.10:22) to root@192.168.159.68(192.168.159.68:22)..
Tue Sep 27 22:58:27 2022 - [debug]   ok.
Tue Sep 27 22:58:27 2022 - [debug]  Connecting via SSH from root@192.168.159.10(192.168.159.10:22) to root@192.168.159.11(192.168.159.11:22)..
Tue Sep 27 22:58:28 2022 - [debug]   ok.
Tue Sep 27 22:58:47 2022 - [debug] 
Tue Sep 27 22:58:26 2022 - [debug]  Connecting via SSH from root@192.168.159.68(192.168.159.68:22) to root@192.168.159.11(192.168.159.11:22)..
Tue Sep 27 22:58:36 2022 - [debug]   ok.
Tue Sep 27 22:58:36 2022 - [debug]  Connecting via SSH from root@192.168.159.68(192.168.159.68:22) to root@192.168.159.10(192.168.159.10:22)..
Tue Sep 27 22:58:47 2022 - [debug]   ok.
Tue Sep 27 22:58:47 2022 - [debug] 
Tue Sep 27 22:58:26 2022 - [debug]  Connecting via SSH from root@192.168.159.11(192.168.159.11:22) to root@192.168.159.68(192.168.159.68:22)..
Tue Sep 27 22:58:37 2022 - [debug]   ok.
Tue Sep 27 22:58:37 2022 - [debug]  Connecting via SSH from root@192.168.159.11(192.168.159.11:22) to root@192.168.159.10(192.168.159.10:22)..
Tue Sep 27 22:58:47 2022 - [debug]   ok.
Tue Sep 27 22:58:47 2022 - [info] All SSH connection tests passed successfully.

最后結(jié)果為tests passed successfully，表示測試正常

2、測試主從復(fù)制

[root@manager conf]# masterha_check_repl -conf=/etc/masterha/app1.cnf
Tue Sep 27 23:00:45 2022 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Sep 27 23:00:45 2022 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Sep 27 23:00:45 2022 - [info] Reading server configuration from 
...............................................................................
Tue Sep 27 23:01:09 2022 - [warning] shutdown_script is not defined.
Tue Sep 27 23:01:09 2022 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

最后測試結(jié)果為;MySQL Replication Health is OK 。 表示測試正常

3、啟動mha

在master節(jié)點(diǎn)上配置ens33：1的虛擬子接口，給與VIP：192.168.159.100/24

[root@manager conf]# nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/masterha/app1/manager.log 2>&1 &
[1] 8982


## 查詢當(dāng)前的master角色
[root@manager conf]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:8982) is running(0:PING_OK), master:192.168.159.68   ## 當(dāng)前master

解釋：
ohup ?? ?//選項?

masterha_manager ?? ?//開啟

--conf=/etc/masterha/app1.cnf ?//指定配置文件

--remove_dead_master_conf //當(dāng)master服務(wù)器失效時，發(fā)生主從切換后，會把舊的master的ip從主配置文件刪

--ignore_last_failover//忽略故障轉(zhuǎn)移，忽略掉總是宕機(jī)不夠可靠的服務(wù)器

4、查看到當(dāng)前的master節(jié)點(diǎn)

[root@manager conf]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:8982) is running(0:PING_OK), master:192.168.159.68

### 當(dāng)前master為192.168.159.68

5、查看當(dāng)前日志信息

[root@manager conf]# tail -f /var/log/masterha/app1/manager.log 

IN SCRIPT TEST====/sbin/ifconfig ens33:1 down==/sbin/ifconfig ens33:1 192.168.159.100===

Checking the Status of the script.. OK 
Tue Sep 27 23:12:10 2022 - [info]  OK.
Tue Sep 27 23:12:10 2022 - [warning] shutdown_script is not defined.
Tue Sep 27 23:12:10 2022 - [info] Set master ping interval 1 seconds.
Tue Sep 27 23:12:10 2022 - [info] Set secondary check script: /usr/local/bin/masterha_secondary_check -s 192.168.159.11 -s 192.168.159.10
Tue Sep 27 23:12:10 2022 - [info] Starting ping health check on 192.168.159.68(192.168.159.68:3306)..
Tue Sep 27 23:12:10 2022 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

6、模擬master宕機(jī)，slave1是否能頂上

①vip在master主機(jī)上

②關(guān)閉master上的MySQL服務(wù)

[root@master ~]# systemctl stop mysqld.service



#####  查看發(fā)現(xiàn)虛擬VIP沒有了



[root@master ~]# ifconfig 
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.159.68  netmask 255.255.255.0  broadcast 192.168.159.255
        inet6 fe80::ce01:2f86:7a80:ce3c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:66:d9:2f  txqueuelen 1000  (Ethernet)
        RX packets 12157  bytes 5819674 (5.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6723  bytes 922189 (900.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 12239  bytes 986082 (962.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12239  bytes 986082 (962.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:44:ba:9b  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

③在原先slave1上查看ifconfig，發(fā)現(xiàn)VIP 漂移過來了。slave1成為了新的master

[root@slave1 ~]# ifconfig 
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.159.11  netmask 255.255.255.0  broadcast 192.168.159.255
        inet6 fe80::8d62:30c7:5d56:1dbb  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:13:31:5e  txqueuelen 1000  (Ethernet)
        RX packets 4734  bytes 600130 (586.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4093  bytes 742333 (724.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.159.100  netmask 255.255.255.0  broadcast 192.168.159.255
        ether 00:0c:29:13:31:5e  txqueuelen 1000  (Ethernet)

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 375  bytes 41807 (40.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 375  bytes 41807 (40.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:bd:1f:d5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

進(jìn)入slave1的數(shù)據(jù)庫中查看狀態(tài)

文章來源地址http://www.zghlxwxcb.cn/news/detail-465205.html

到了這里，關(guān)于MHA高可用架構(gòu)部署以及配置(詳細(xì))的文章就介紹完了。如果您還想了解更多內(nèi)容，請在右上角搜索TOY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關(guān)文章，希望大家以后多多支持TOY模板網(wǎng)！