共計 19003 個字符，預計需要花費 48 分鐘才能閱讀完成。
丸趣 TV 小編給大家分享一下 MySQL 中 HA MHA 如何搭建，相信大部分人都還不怎么了解，因此分享這篇文章給大家參考一下，希望大家閱讀完這篇文章后大有收獲，下面讓我們一起去了解一下吧！
mha 結構恢復過程：
mha 架構圖：
本次測試環境為 3 臺服務器
其中將一臺 slave 作為 mha 中的 manager 節點
————————————–
ip hostname mysql
————————————–
10.1.10.244 data01 master
10.1.10.80 data02 slave
10.1.10.91 manager slave
————————————–
主機情況：
服務器發行版：centos6.7
內核：2.6.32-220.el6.x86_64
數據庫軟件版本：MySQL Community 5.6.29
————————————- 修改主機名 ————————————-
undefined
244(master):
# vi /etc/sysconfig/network
將 HOSTNAME 修改為 data01
80(slave):
# vi /etc/sysconfig/network
將 HOSTNAME 修改為 data02
91(slave):
# vi /etc/sysconfig/network
將 HOSTNAME 修改為 manager
同時修改三臺服務器 hosts：
# vi /etc/hosts
添加：
10.1.10.244 data01
10.1.10.80 data02
10.1.10.91 manager
————————————- 建立互信關系 ————————————-
在三臺服務器上分別執行：
244(master)、80(slave)、91(slave):
# cd /root/.ssh
# ssh-keygen -t rsa
全部默認，直接回車
在 224(master)上執行:
# cd /root/.ssh
# cat id_dsa.pub authorized_keys
# scp root@10.1.10.80:/root/.ssh/id_dsa.pub ./id_dsa.pub.data02.80
# scp root@10.1.10.91:/root/.ssh/id_dsa.pub ./id_dsa.pub.manager.91
# cat id_dsa.pub.data02.80 authorized_keys
# cat id_dsa.pub.manager.91 authorized_keys
# scp authorized_keys root@10.1.10.80:/root/.ssh/authorized_keys
# scp authorized_keys root@10.1.10.91:/root/.ssh/authorized_keys
從 244(master)開始兩兩驗證：
[root@data01 ~]# ssh data02
……略……
[root@data02 ~]# ssh manager
……略……
[root@manager ~]# ssh data01
……略……
[root@data01 ~]# ssh manager
……略……
[root@manager ~]# ssh data02
……略……
[root@data02 ~]# ssh data01
……略……
————————————- 建立主從關系 ————————————-
在三臺服務器上的 mysql-server 上分別執行：
244(master)、80(slave)、91(slave):
mysql GRANT super, replication slave, reload ON *.* TO repl_user@ 10.1.10.% IDENTIFIED BY repl_user
Query OK, 0 rows affected (0.00 sec)
mysql FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
分別修改三臺服務器上 mysql 的配置文件：
244(master):
[mysqld]
log-bin = /var/lib/mysql/data01-bin
log-bin-index = /var/lib/mysql/data01-bin.index
server-id = 244
relay-log = /var/lib/mysql/data01-relay-bin
relay-log-index = /var/lib/mysql/data01-relay-bin.index
log-slave-updates
80(slave):
[mysqld]
log-bin = /var/lib/mysql/data02-bin
log-bin-index = /var/lib/mysql/data02-bin.index
server-id = 80
relay-log = /var/lib/mysql/data02-relay-bin
relay-log-index = /var/lib/mysql/data02-relay-bin.index
log-slave-updates
91(slave):
[mysqld]
log-bin = /var/lib/mysql/manager-bin
log-bin-index = /var/lib/mysql/manager-bin.index
server-id = 91
relay-log = /var/lib/mysql/manager-relay-bin
relay-log-index = /var/lib/mysql/manager-relay-bin.index
log-slave-updates
在兩臺 slave 上分別執行：
80(slave)、91(slave):
mysql CHANGE MASTER TO
– MASTER_HOST = 10.1.10.244 ,
– MASTER_PORT = 3306,
– MASTER_USER = repl_user ,
– MASTER_PASSWORD = repl_user
Query OK, 0 rows affected, 2 warnings (0.03 sec)
mysql START SLAVE;
Query OK, 0 rows affected (0.00 sec)
執行完后可以查看一下復制進程是否出問題：
mysql SHOW SLAVE STATUS\G
若顯示 IO 和 SQL 線程為 Yes 則表示復制建立好了：
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
也可以通過 SHOW PROCESSLIST 來看。
————————————- 安裝 mha-manager 及 mha-node ————————————-
即將需要用到的附件：
mha4mysql-node-0.56.tar.gz
mha4mysql-manager-0.56.tar.gz
這兩個 tar 包可以搜一下
在三臺服務器上分別執行：
244(data01)、80(data02)、91(manager):
# yum install -y perl-DBD-MySQL
繼續分別在三臺服務器上安裝 mha-node 工具：
mha-node 安裝：
# tar zxvf mha4mysql-node-0.56.tar.gz
# cd mha4mysql-node-0.56
# perl Makefile.PL
# make make install
在管理服務器上安裝 mha-manager 工具：
91(manager):
先在 manager 服務器上安裝一些依賴工具或 perl 模塊：
# yum install -y perl-Config-Tiny
以下三個可能安不上：
# yum install -y perl-Log-Dispatch
# yum install -y perl-Parallel-ForkManager
# yum install -y perl-Config-IniFiles
可以通過 perl CPAN 來安裝，如果沒有，要先通過 yum 安裝一下 CPAN：
# yum install -y perl-CPAN
進入 CPAN 來安裝 perl 模塊：
# perl -MCPAN -e shell
cpan[1] install Log::Dispatch
cpan[1] install Parallel::ForkManager
cpan[1] install Config::IniFiles
如果安裝失敗，可以根據提示信息，先安裝一些依賴模塊，暫時總結如下（CPAN 中）：
install Test::Requires
install Module::Runtime
install Dist::CheckConflicts
install Params::Validate
install Module::Runtime
install Module::Implementation
install ExtUtils::MakeMaker
mha-manger 安裝：
# tar zxvf mha4mysql-manager-0.56.tar.gz
# cd mha4mysql-manager-0.56
# perl Makefile.PL
通過檢查 Makefile.PL 可以得知之前的模塊是否安裝成功。
檢查效果如下：
…………
[Core Features]
– DBI …loaded. (1.609)
– DBD::mysql …loaded. (4.013)
– Time::HiRes …loaded. (1.9728)
– Config::Tiny …loaded. (2.12)
– Log::Dispatch …loaded. (2.54)
– Parallel::ForkManager …loaded. (1.17)
– MHA::NodeConst …loaded. (0.56)
…………
如果 missing 則表示缺少。
如果都 ok，則編譯：
# make make install
————————————- 添加 mha 配置文件 ————————————-
在管理服務器上配置：
91(manager):
# mkdir /var/log/mha
# vi /etc/mha-manger.cnf
此次實驗僅一個節點，若多個節點可以改一下 manager 服務器的配置文件結構：
touch /etc/masterha_default.cnf 寫 [server default]
touch /etc/node1.cnf 寫該節點上的 server 信息，如[server_1]、[server_2] 等
分別用 –global_conf=/etc/masterha_default.cnf –conf=/etc/node1.cnf 來使用
——– 配置文件 ——–
[server default]
manager_workdir = /var/log/mha/
manager_log = /var/log/mha/manager.log
ssh_user = root
repl_user = repl_user
repl_password = repl_user
[server_1]
hostname = 10.1.10.244
user = root
password = root
candidate_master = 1
master_binlog_dir = /var/lib/mysql
[server_2]
hostname = 10.1.10.80
user = root
password = root
#candidate_master = 1
master_binlog_dir = /var/lib/mysql
[server_3]
hostname = 10.1.10.91
user = root
password = root
#candidate_master = 1
master_binlog_dir = /var/lib/mysql
其他參數此處取默認值，更多參數可查閱本文結尾處的參考文檔。
——– 配置文件 ——–
undefined
# masterha_check_ssh –conf=/etc/mha-manager.cnf
– [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
– [info] Reading application default configuration from /etc/mha-manager.cnf..
– [info] Reading server configuration from /etc/mha-manager.cnf..
– [info] Starting SSH connection tests..
– [debug]
– [debug] Connecting via SSH from root@10.1.10.244(10.1.10.244:22) to root@10.1.10.80(10.1.10.80:22)..
– [debug] ok.
– [debug] Connecting via SSH from root@10.1.10.244(10.1.10.244:22) to root@10.1.10.91(10.1.10.91:22)..
– [debug] ok.
– [debug]
– [debug] Connecting via SSH from root@10.1.10.80(10.1.10.80:22) to root@10.1.10.244(10.1.10.244:22)..
– [debug] ok.
– [debug] Connecting via SSH from root@10.1.10.80(10.1.10.80:22) to root@10.1.10.91(10.1.10.91:22)..
– [debug] ok.
– [debug]
– [debug] Connecting via SSH from root@10.1.10.91(10.1.10.91:22) to root@10.1.10.244(10.1.10.244:22)..
Warning: Permanently added 10.1.10.91 (RSA) to the list of known hosts.
– [debug] ok.
– [debug] Connecting via SSH from root@10.1.10.91(10.1.10.91:22) to root@10.1.10.80(10.1.10.80:22)..
– [debug] ok.
– [info] All SSH connection tests passed successfully.
繼續檢查復制是否通：
# masterha_check_repl –conf=/etc/mha-manager.cnf
若看到【MySQL Replication Health is OK.】則表示成功連通。
若失敗，則可以從防火墻，對應 mysql 服務器用戶權限，對應操作系統用戶對文件的讀寫權限等方面排查。
————————————- 管理 manager ————————————-
繼續在管理服務器上啟動：
91(manager):
啟動 manager：
# nohup masterha_manager –conf=/etc/mha-manager.cnf /var/log/mha/manager.log 2 1
檢查進程：
# ps -ef | grep manager
root 18210 10044 0 18:11 pts/1 00:00:00 perl /usr/local/bin/masterha_manager –conf=/etc/mha-manager.cnf /var/log/mha/manager.log
可以看一下最后的日志情況：
# tail -20 /var/log/mha/manager.log
……………………
Thu Feb 18 18:11:37 2016 – [info] Ping(SELECT) succeeded, waiting until MySQL doesn t respond..
繼續檢查 master 狀態：
# masterha_check_status –conf=/etc/mha-manager.cnf
mha-manager (pid:18210) is running(0:PING_OK), master:10.1.10.244
關閉 manager：
# masterha_stop –conf=/etc/mha-manager.cnf
Stopped mha-manager successfully.
————————————- failover 檢測 ————————————-
此處模擬服務器整個宕機
操作：直接重啟 master 服務器（此處是 data01，即 244）
通過 tail - f 查看 mha-manager.log 日志，刷出來如下記錄：
Thu Feb 18 18:23:37 2016 – [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)
Thu Feb 18 18:23:37 2016 – [info] Executing SSH check script: save_binary_logs –command=test –start_pos=4 –binlog_dir=/var/lib/mysql –output_file=/var/tmp/save_binary_logs_test –manager_version=0.56 –binlog_prefix=data01-bin
Thu Feb 18 18:23:37 2016 – [warning] HealthCheck: SSH to 10.1.10.244 is NOT reachable.
Thu Feb 18 18:23:43 2016 – [warning] Got error on MySQL connect: 2003 (Can t connect to MySQL server on 10.1.10.244 (4))
Thu Feb 18 18:23:43 2016 – [warning] Connection failed 2 time(s)..
Thu Feb 18 18:23:46 2016 – [warning] Got error on MySQL connect: 2003 (Can t connect to MySQL server on 10.1.10.244 (4))
Thu Feb 18 18:23:46 2016 – [warning] Connection failed 3 time(s)..
Thu Feb 18 18:23:49 2016 – [warning] Got error on MySQL connect: 2003 (Can t connect to MySQL server on 10.1.10.244 (4))
Thu Feb 18 18:23:49 2016 – [warning] Connection failed 4 time(s)..
Thu Feb 18 18:23:49 2016 – [warning] Master is not reachable from health checker!
Thu Feb 18 18:23:49 2016 – [warning] Master 10.1.10.244(10.1.10.244:3306) is not reachable!
Thu Feb 18 18:23:49 2016 – [warning] SSH is NOT reachable.
Thu Feb 18 18:23:49 2016 – [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha-manager.cnf again, and trying to connect to all servers to check server status..
Thu Feb 18 18:23:49 2016 – [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Feb 18 18:23:49 2016 – [info] Reading application default configuration from /etc/mha-manager.cnf..
Thu Feb 18 18:23:49 2016 – [info] Reading server configuration from /etc/mha-manager.cnf..
Thu Feb 18 18:23:50 2016 – [info] GTID failover mode = 0
Thu Feb 18 18:23:50 2016 – [info] Dead Servers:
Thu Feb 18 18:23:50 2016 – [info] 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:50 2016 – [info] Alive Servers:
Thu Feb 18 18:23:50 2016 – [info] 10.1.10.80(10.1.10.80:3306)
Thu Feb 18 18:23:50 2016 – [info] 10.1.10.91(10.1.10.91:3306)
Thu Feb 18 18:23:50 2016 – [info] Alive Slaves:
Thu Feb 18 18:23:50 2016 – [info] 10.1.10.80(10.1.10.80:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:50 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:50 2016 – [info] 10.1.10.91(10.1.10.91:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:50 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:50 2016 – [info] Checking slave configurations..
Thu Feb 18 18:23:50 2016 – [info] read_only=1 is not set on slave 10.1.10.80(10.1.10.80:3306).
Thu Feb 18 18:23:50 2016 – [warning] relay_log_purge=0 is not set on slave 10.1.10.80(10.1.10.80:3306).
Thu Feb 18 18:23:50 2016 – [info] read_only=1 is not set on slave 10.1.10.91(10.1.10.91:3306).
Thu Feb 18 18:23:50 2016 – [warning] relay_log_purge=0 is not set on slave 10.1.10.91(10.1.10.91:3306).
Thu Feb 18 18:23:50 2016 – [info] Checking replication filtering settings..
Thu Feb 18 18:23:50 2016 – [info] Replication filtering check ok.
Thu Feb 18 18:23:50 2016 – [info] Master is down!
Thu Feb 18 18:23:50 2016 – [info] Terminating monitoring script.
Thu Feb 18 18:23:50 2016 – [info] Got exit code 20 (Master dead).
Thu Feb 18 18:23:50 2016 – [info] MHA::MasterFailover version 0.56.
Thu Feb 18 18:23:50 2016 – [info] Starting master failover.
Thu Feb 18 18:23:50 2016 – [info]
Thu Feb 18 18:23:50 2016 – [info] * Phase 1: Configuration Check Phase..
Thu Feb 18 18:23:50 2016 – [info]
Thu Feb 18 18:23:51 2016 – [info] GTID failover mode = 0
Thu Feb 18 18:23:51 2016 – [info] Dead Servers:
Thu Feb 18 18:23:51 2016 – [info] 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:51 2016 – [info] Checking master reachability via MySQL(double check)…
Thu Feb 18 18:23:52 2016 – [info] ok.
Thu Feb 18 18:23:52 2016 – [info] Alive Servers:
Thu Feb 18 18:23:52 2016 – [info] 10.1.10.80(10.1.10.80:3306)
Thu Feb 18 18:23:52 2016 – [info] 10.1.10.91(10.1.10.91:3306)
Thu Feb 18 18:23:52 2016 – [info] Alive Slaves:
Thu Feb 18 18:23:52 2016 – [info] 10.1.10.80(10.1.10.80:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:52 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:52 2016 – [info] 10.1.10.91(10.1.10.91:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:52 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:52 2016 – [info] Starting Non-GTID based failover.
Thu Feb 18 18:23:52 2016 – [info]
Thu Feb 18 18:23:52 2016 – [info] ** Phase 1: Configuration Check Phase completed.
Thu Feb 18 18:23:52 2016 – [info]
Thu Feb 18 18:23:52 2016 – [info] * Phase 2: Dead Master Shutdown Phase..
Thu Feb 18 18:23:52 2016 – [info]
Thu Feb 18 18:23:52 2016 – [info] Forcing shutdown so that applications never connect to the current master..
Thu Feb 18 18:23:52 2016 – [warning] master_ip_failover_script is not set. Skipping invalidating dead master IP address.
Thu Feb 18 18:23:52 2016 – [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Thu Feb 18 18:23:53 2016 – [info] * Phase 2: Dead Master Shutdown Phase completed.
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3: Master Recovery Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3.1: Getting Latest Slaves Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] The latest binary log file/position on all slaves is data01-bin.000016:120
Thu Feb 18 18:23:53 2016 – [info] Latest slaves (Slaves that received relay log files to the latest):
Thu Feb 18 18:23:53 2016 – [info] 10.1.10.80(10.1.10.80:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:53 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:53 2016 – [info] 10.1.10.91(10.1.10.91:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:53 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:53 2016 – [info] The oldest binary log file/position on all slaves is data01-bin.000016:120
Thu Feb 18 18:23:53 2016 – [info] Oldest slaves:
Thu Feb 18 18:23:53 2016 – [info] 10.1.10.80(10.1.10.80:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:53 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:53 2016 – [info] 10.1.10.91(10.1.10.91:3306) Version=5.6.29-log (oldest major version between slaves) log-bin:enabled
Thu Feb 18 18:23:53 2016 – [info] Replicating from 10.1.10.244(10.1.10.244:3306)
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3.2: Saving Dead Master s Binlog Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [warning] Dead Master is not SSH reachable. Could not save it s binlogs. Transactions that were not sent to the latest slave (Read_Master_Log_Pos to the tail of the dead master s binlog) were lost.
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3.3: Determining New Master Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] Finding the latest slave that has all relay logs for recovering other slaves..
Thu Feb 18 18:23:53 2016 – [info] All slaves received relay logs to the same position. No need to resync each other.
Thu Feb 18 18:23:53 2016 – [info] Searching new master from slaves..
Thu Feb 18 18:23:53 2016 – [info] Candidate masters from the configuration file:
Thu Feb 18 18:23:53 2016 – [info] Non-candidate masters:
Thu Feb 18 18:23:53 2016 – [info] New master is 10.1.10.80(10.1.10.80:3306)
Thu Feb 18 18:23:53 2016 – [info] Starting master failover..
Thu Feb 18 18:23:53 2016 – [info]
From:
10.1.10.244(10.1.10.244:3306) (current master)
+–10.1.10.80(10.1.10.80:3306)
+–10.1.10.91(10.1.10.91:3306)
To:
10.1.10.80(10.1.10.80:3306) (new master)
+–10.1.10.91(10.1.10.91:3306)
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3.3: New Master Diff Log Generation Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 3.4: Master Log Apply Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Thu Feb 18 18:23:53 2016 – [info] Starting recovery on 10.1.10.80(10.1.10.80:3306)..
Thu Feb 18 18:23:53 2016 – [info] This server has all relay logs. Waiting all logs to be applied..
Thu Feb 18 18:23:53 2016 – [info] done.
Thu Feb 18 18:23:53 2016 – [info] All relay logs were successfully applied.
Thu Feb 18 18:23:53 2016 – [info] Getting new master s binlog name and position..
Thu Feb 18 18:23:53 2016 – [info] data02-bin.000003:684
Thu Feb 18 18:23:53 2016 – [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST= 10.1.10.80 , MASTER_PORT=3306, MASTER_LOG_FILE= data02-bin.000003 , MASTER_LOG_POS=684, MASTER_USER= repl_user , MASTER_PASSWORD= xxx
Thu Feb 18 18:23:53 2016 – [warning] master_ip_failover_script is not set. Skipping taking over new master IP address.
Thu Feb 18 18:23:53 2016 – [info] ** Finished master recovery successfully.
Thu Feb 18 18:23:53 2016 – [info] * Phase 3: Master Recovery Phase completed.
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 4: Slaves Recovery Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Thu Feb 18 18:23:53 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] — Slave diff file generation on host 10.1.10.91(10.1.10.91:3306) started, pid: 18577. Check tmp log /var/log/mha//10.1.10.91_3306_20160218182350.log if it takes time..
Thu Feb 18 18:23:54 2016 – [info]
Thu Feb 18 18:23:54 2016 – [info] Log messages from 10.1.10.91 …
Thu Feb 18 18:23:54 2016 – [info]
Thu Feb 18 18:23:53 2016 – [info] This server has all relay logs. No need to generate diff files from the latest slave.
Thu Feb 18 18:23:54 2016 – [info] End of log messages from 10.1.10.91.
Thu Feb 18 18:23:54 2016 – [info] — 10.1.10.91(10.1.10.91:3306) has the latest relay log events.
Thu Feb 18 18:23:54 2016 – [info] Generating relay diff files from the latest slave succeeded.
Thu Feb 18 18:23:54 2016 – [info]
Thu Feb 18 18:23:54 2016 – [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Thu Feb 18 18:23:54 2016 – [info]
Thu Feb 18 18:23:54 2016 – [info] — Slave recovery on host 10.1.10.91(10.1.10.91:3306) started, pid: 18579. Check tmp log /var/log/mha//10.1.10.91_3306_20160218182350.log if it takes time..
Thu Feb 18 18:23:55 2016 – [info]
Thu Feb 18 18:23:55 2016 – [info] Log messages from 10.1.10.91 …
Thu Feb 18 18:23:55 2016 – [info]
Thu Feb 18 18:23:54 2016 – [info] Starting recovery on 10.1.10.91(10.1.10.91:3306)..
Thu Feb 18 18:23:54 2016 – [info] This server has all relay logs. Waiting all logs to be applied..
Thu Feb 18 18:23:54 2016 – [info] done.
Thu Feb 18 18:23:54 2016 – [info] All relay logs were successfully applied.
Thu Feb 18 18:23:54 2016 – [info] Resetting slave 10.1.10.91(10.1.10.91:3306) and starting replication from the new master 10.1.10.80(10.1.10.80:3306)..
Thu Feb 18 18:23:54 2016 – [info] Executed CHANGE MASTER.
Thu Feb 18 18:23:54 2016 – [info] Slave started.
Thu Feb 18 18:23:55 2016 – [info] End of log messages from 10.1.10.91.
Thu Feb 18 18:23:55 2016 – [info] — Slave recovery on host 10.1.10.91(10.1.10.91:3306) succeeded.
Thu Feb 18 18:23:55 2016 – [info] All new slave servers recovered successfully.
Thu Feb 18 18:23:55 2016 – [info]
Thu Feb 18 18:23:55 2016 – [info] * Phase 5: New master cleanup phase..
Thu Feb 18 18:23:55 2016 – [info]
Thu Feb 18 18:23:55 2016 – [info] Resetting slave info on the new master..
Thu Feb 18 18:23:55 2016 – [info] 10.1.10.80: Resetting slave info succeeded.
Thu Feb 18 18:23:55 2016 – [info] Master failover to 10.1.10.80(10.1.10.80:3306) completed successfully.
Thu Feb 18 18:23:55 2016 – [info]
—– Failover Report —–
mha-manager: MySQL Master failover 10.1.10.244(10.1.10.244:3306) to 10.1.10.80(10.1.10.80:3306) succeeded
Master 10.1.10.244(10.1.10.244:3306) is down!
Check MHA Manager logs at manager:/var/log/mha/manager.log for details.
Started automated(non-interactive) failover.
The latest slave 10.1.10.80(10.1.10.80:3306) has all relay logs for recovery.
Selected 10.1.10.80(10.1.10.80:3306) as a new master.
10.1.10.80(10.1.10.80:3306): OK: Applying all logs succeeded.
10.1.10.91(10.1.10.91:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
10.1.10.91(10.1.10.91:3306): OK: Applying all logs succeeded. Slave started, replicating from 10.1.10.80(10.1.10.80:3306)
10.1.10.80(10.1.10.80:3306): Resetting slave info succeeded.
Master failover to 10.1.10.80(10.1.10.80:3306) completed successfully.
模擬結束
測的不太多，目前知道的一個坑：
mha 建議關閉 relay_log_purge，以保證用于有足夠的中繼日志去恢復其他的從庫，也就是需要將 relay_log_purge=0，導致 relay-log 無法定期清理。
可能需要手動添加定時任務來清理，清理方式可以是：
……/purge_relay_logs –user=$user –password=$password–disable_relay_log_purge ……/log/purge_relay_logs.log 2 1
當然還需要配合 vip 節點等保證應用透明性，實現 failover。
以上是“MySQL 中 HA MHA 如何搭建”這篇文章的所有內容，感謝各位的閱讀！相信大家都有了一定的了解，希望分享的內容對大家有所幫助，如果還想學習更多知識，歡迎關注丸趣 TV 行業資訊頻道！
