簡介：
MHA（Master High Availability）目前在MySQL高可用方面是一個相對成熟的解決方案，它由日本DeNA公司youshimaton（現就職於Facebook公司）開發，是一套優秀的作爲MySQL高可用性環境下故障切換和主從提升的高可用軟件。在MySQL故障切換過程中，MHA能做到在0~30秒之內自動完成數據庫的故障切換操作，並且在進行故障切換的過程中，MHA能在最大程度上保證數據的一致性，以達到真正意義上的高可用。
該軟件由兩部分組成：MHA Manager（管理節點）和MHA Node（數據節點）。MHA Manager可以單獨部署在一臺獨立的機器上管理多個master-slave集羣，也可以部署在一臺slave節點上。MHA Node運行在每臺MySQL服務器上，MHA Manager會定時探測集羣中的master節點，當master出現故障時，它可以自動將最新數據的slave提升爲新的master，然後將所有其他的slave重新指向新的master。整個故障轉移過程對應用程序完全透明。
在MHA自動故障切換過程中，MHA試圖從宕機的主服務器上保存二進制日誌，最大程度的保證數據的不丟失，但這並不總是可行的。例如，如果主服務器硬件故障或無法通過ssh訪問，MHA沒法保存二進制日誌，只進行故障轉移而丟失了最新的數據。使用MySQL 5.5的半同步複製，可以大大降低數據丟失的風險。MHA可以與半同步複製結合起來。如果只有一個slave已經收到了最新的二進制日誌，MHA可以將最新的二進制日誌應用於其他所有的slave服務器上，因此可以保證所有節點的數據一致性。
目前MHA主要支持一主多從的架構，要搭建MHA,要求一個複製集羣中必須最少有三臺數據庫服務器，一主二從，即一臺充當master，一臺充當備用master，另外一臺充當從庫，因爲至少需要三臺服務器，出於機器成本的考慮，淘寶也在該基礎上進行了改造，目前淘寶TMHA已經支持一主一從。另外對於想快速搭建的可以參考：MHA快速搭建
我們自己使用其實也可以使用1主1從，但是master主機宕機後無法切換，以及無法補全binlog。master的mysqld進程crash後，還是可以切換成功，以及補全binlog的。
在所有node節點安裝MHA node所需的perl模塊（DBD:mysql）
yum install perl-DBD-MySQL -y
在所有的節點安裝mha node
https://github.com/yoshinorim/mha4mysql-manager/wiki/Downloads [root@manager ~]# cd /application/tools/ [root@manager tools]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm [root@master1 ~]# cd /application/tools/ [root@master1 tools]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm [root@master2 ~]# cd /application/tools/ [root@master2 tools]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm [root@slave ~]# cd /application/tools/ [root@slave tools]# rpm -ivh mha4mysql-node-0.56-0.el6.noarch.rpm
配置SSH登錄無密碼驗證
manager echo -e "\n" | ssh-keygen rsa -N "" ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] master1 echo -e "\n" | ssh-keygen rsa -N "" ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] master2 echo -e "\n" | ssh-keygen rsa -N "" ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] slave echo -e "\n" | ssh-keygen rsa -N "" ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected] ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected]
安裝MHA Manager軟件包
https://github.com/yoshinorim/mha4mysql-manager/wiki/Downloads [root@manager ~]# yum install perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Time-HiRes -y [root@manager ~]# cd /application/tools/ [root@manager tools]# rpm -ivh mha4mysql-manager-0.56-0.el6.noarch.rpm 安裝後會在/usr/bin下生成如下腳本文件 rpm -qpl mha4mysql-manager-0.56-0.el6.noarch.rpm /usr/bin/masterha_check_repl /usr/bin/masterha_check_ssh /usr/bin/masterha_check_status /usr/bin/masterha_conf_host /usr/bin/masterha_manager /usr/bin/masterha_master_monitor /usr/bin/masterha_master_switch /usr/bin/masterha_secondary_check /usr/bin/masterha_stop
創建監控用戶
master1 grant all privileges on *.* to 'root'@'172.16.1.%' identified by '123456'; flush privileges;
創建MHA的工作目錄，並且創建相關配置文件
manager [root@manager ~]# mkdir -p /etc/masterha [root@manager ~]# cat /etc/masterha/app1.cnf [server default] manager_workdir=/var/log/masterha/app1.log //設置manager的工作目錄 manager_log=/var/log/masterha/app1/manager.log //設置manager的日誌 master_binlog_dir=/application/mysql/data //設置master 保存binlog的位置，以便MHA可以找到master的日誌，我這裏的也就是mysql的數據目錄 master_ip_failover_script= /usr/bin/master_ip_failover //設置自動failover時候的切換腳本 master_ip_online_change_script= /usr/bin/master_ip_online_change //設置手動切換時候的切換腳本 password=123456 //設置mysql中root用戶的密碼，這個密碼是前文中創建監控用戶的那個密碼 user=root //設置監控用戶root ping_interval=1 //設置監控主庫，發送ping包的時間間隔，默認是3秒，嘗試三次沒有迴應的時候自動進行railover remote_workdir=/tmp //設置遠端mysql在發生切換時binlog的保存位置 repl_password=mysql01 //設置複製用戶的密碼 repl_user=mysql01 //設置複製環境中的複製用戶名 report_script=/usr/bin/send_report //設置發生切換後發送的報警的腳本 secondary_check_script=/usr/bin/masterha_secondary_check -s 172.16.1.104 --user=root --master_host=172.16.1.103 --master_ip=172.16.1.103 --master_port=3306 //一旦MHA到master的監控之間出現問題 MHAManager將會判斷其它兩個slave是否能建立到master3306端口的連接 shutdown_script="" //設置故障發生後關閉故障主機腳本（該腳本的主要作用是關閉主機放在發生腦裂,這裏沒有使用） ssh_user=root //設置ssh的登錄用戶名 [server1] hostname=172.16.1.103 port=3306 [server2] hostname=172.16.1.104 port=3306 candidate_master=1 //設置爲候選master，如果設置該參數以後，發生主從切換以後將會將此從庫提升爲主庫 check_repl_delay=0 //這個候選主在切換的過程中一定是新的master [server3] hostname=172.16.1.105 port=3306
上面設置的腳本內容
上述腳本需要添加執行權限
chmod +x /usr/bin/master_ip_failover chmod +x /usr/bin/master_ip_online_change chmod +x /usr/bin/send_report
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 = '172.16.1.200/24'; # Virtual IP
my $key = "1";
my $ssh_start_vip = "/sbin/ifconfig eth1:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig eth1:$key down";
my $exit_code = 0;
$ssh_user = "root";
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" ) {
# $orig_master_host, $orig_master_ip, $orig_master_port are passed.
# If you manage master ip address at global catalog database,
# invalidate orig_master_ip here.
my $exit_code = 1;
eval {
print "\n\n\n***************************************************************\n";
print "Disabling the VIP - $vip on old master: $orig_master_host\n";
print "***************************************************************\n\n\n\n";
&stop_vip();
$exit_code = 0;
};
if ($@) {
warn "Got Error: $@\n";
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "start" ) {
# all arguments are passed.
# If you manage master ip address at global catalog database,
# activate new_master_ip here.
# You can also grant write access (create user, set read_only=0, etc) here.
my $exit_code = 10;
eval {
print "\n\n\n***************************************************************\n";
print "Enabling the VIP - $vip on new master: $new_master_host \n";
print "***************************************************************\n\n\n\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";
`ssh $ssh_user\@$orig_master_host \" $ssh_start_vip \"`;
exit 0;
}
else {
&usage();
exit 1;
}
}
# A simple system call that enable the VIP on the new master
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=po
rt –new_master_host=host –new_master_ip=ip –new_master_port=port\n";
}master_ip_online_change
#!/usr/bin/env perl
use strict;
use warnings FATAL =>'all';
use Getopt::Long;
my $vip = '172.16.1.200/24'; # Virtual IP
my $key = "1";
my $ssh_start_vip = "/sbin/ifconfig eth1:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig eth1:$key down";
my $exit_code = 0;
$ssh_user = "root";
my (
$command, $orig_master_is_new_slave, $orig_master_host,
$orig_master_ip, $orig_master_port, $orig_master_user,
$orig_master_password, $orig_master_ssh_user, $new_master_host,
$new_master_ip, $new_master_port, $new_master_user,
$new_master_password, $new_master_ssh_user,
);
GetOptions(
'command=s' => \$command,
'orig_master_is_new_slave' => \$orig_master_is_new_slave,
'orig_master_host=s' => \$orig_master_host,
'orig_master_ip=s' => \$orig_master_ip,
'orig_master_port=i' => \$orig_master_port,
'orig_master_user=s' => \$orig_master_user,
'orig_master_password=s' => \$orig_master_password,
'orig_master_ssh_user=s' => \$orig_master_ssh_user,
'new_master_host=s' => \$new_master_host,
'new_master_ip=s' => \$new_master_ip,
'new_master_port=i' => \$new_master_port,
'new_master_user=s' => \$new_master_user,
'new_master_password=s' => \$new_master_password,
'new_master_ssh_user=s' => \$new_master_ssh_user,
);
exit &main();
sub main {
#print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";
if ( $command eq "stop" || $command eq "stopssh" ) {
# $orig_master_host, $orig_master_ip, $orig_master_port are passed.
# If you manage master ip address at global catalog database,
# invalidate orig_master_ip here.
my $exit_code = 1;
eval {
print "\n\n\n***************************************************************\n";
print "Disabling the VIP - $vip on old master: $orig_master_host\n";
print "***************************************************************\n\n\n\n";
&stop_vip();
$exit_code = 0;
};
if ($@) {
warn "Got Error: $@\n";
exit $exit_code;
}
exit $exit_code;
}
elsif ( $command eq "start" ) {
# all arguments are passed.
# If you manage master ip address at global catalog database,
# activate new_master_ip here.
# You can also grant write access (create user, set read_only=0, etc) here.
my $exit_code = 10;
eval {
print "\n\n\n***************************************************************\n";
print "Enabling the VIP - $vip on new master: $new_master_host \n";
print "***************************************************************\n\n\n\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";
`ssh $orig_master_ssh_user\@$orig_master_host \" $ssh_start_vip \"`;
exit 0;
}
else {
&usage();
exit 1;
}
}
# A simple system call that enable the VIP on the new master
sub start_vip() {
`ssh $new_master_ssh_user\@$new_master_host \" $ssh_start_vip \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`ssh $orig_master_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=po
rt ?new_master_host=host ?new_master_ip=ip ?new_master_port=port\n";
}send_report
#/bin/bash
source /root/.bash_profile
orig_master_host=`echo "$1" | awk -F = '{print $2}'`
new_master_host=`echo "$2" | awk -F = '{print $2}'`
new_slave_hosts=`echo "$3" | awk -F = '{print $2}'`
subject=`echo "$4" | awk -F = '{print $2}'`
body=`echo "$5" | awk -F = '{print $2}'`
#判斷日誌結尾是否有successfully，有則表示切換成功，成功與否都發郵件。
tac /var/log/masterha/app1/manager.log | sed -n 2p | grep 'successfully' > /dev/null
if [ $? -eq 0 ]
then
echo -e "MHA $subject 主從切換成功\n master:$orig_master_host --> $new_master_host \n $body \n 當前從庫:$new_slave_hosts 如果 確定主庫可以恢復 請執行 sh /server/scripts/recover.sh 完成主庫的恢復 重新作爲新主庫的從庫 重新加入集羣"| mail -s "MySQL實例宕掉,MHA $subject 切換成功" [email protected]
else
echo -e "MHA $subject 主從切換失敗\n master:$orig_master_host --> $new_master_host \n $body" | mail -s "MySQL實例宕掉,MHA $subject 切換失敗" [email protected]
fi郵件設置
set [email protected] set smtp=smtp.163.com set [email protected] set smtp-auth-password=a625013463 set smtp-auth=login
設置定期清理relay（兩臺slave服務器，relay_log_purge=0已經寫到配置文件中）
[root@master2 ~]# echo '0 5 * * * /usr/bin/purge_relay_logs --user=root --password=123456 --disable_relay_log_purge >> /application/mysql/log/mysql-del-relay.log 2>&1' >> /var/spool/cron/root [root@master2 ~]# crontab -l */5 * * * * /usr/sbin/ntpdate 0.asia.pool.ntp.org >/dev/null 2>&1 0 5 * * * /usr/bin/purge_relay_logs --user=root --password=123456 --disable_relay_log_purge >> /application/mysql/log/mysql-del-relay.log 2>&1 [root@master2 ~]#
檢查MHA Manger到所有MHA Node的SSH連接狀態
[root@manager ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf Sat May 12 14:30:04 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Sat May 12 14:30:04 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf.. Sat May 12 14:30:04 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf.. Sat May 12 14:30:04 2018 - [info] Starting SSH connection tests.. Sat May 12 14:30:06 2018 - [debug] Sat May 12 14:30:04 2018 - [debug] Connecting via SSH from [email protected](172.16.1.103:22) to [email protected](172.16.1.104:22).. Sat May 12 14:30:05 2018 - [debug] ok. Sat May 12 14:30:05 2018 - [debug] Connecting via SSH from [email protected](172.16.1.103:22) to [email protected](172.16.1.105:22).. Warning: Permanently added '172.16.1.105' (RSA) to the list of known hosts. Sat May 12 14:30:05 2018 - [debug] ok. Sat May 12 14:30:06 2018 - [debug] Sat May 12 14:30:05 2018 - [debug] Connecting via SSH from [email protected](172.16.1.104:22) to [email protected](172.16.1.103:22).. Sat May 12 14:30:05 2018 - [debug] ok. Sat May 12 14:30:05 2018 - [debug] Connecting via SSH from [email protected](172.16.1.104:22) to [email protected](172.16.1.105:22).. Warning: Permanently added '172.16.1.105' (RSA) to the list of known hosts. Sat May 12 14:30:06 2018 - [debug] ok. Sat May 12 14:30:06 2018 - [debug] Sat May 12 14:30:05 2018 - [debug] Connecting via SSH from [email protected](172.16.1.105:22) to [email protected](172.16.1.103:22).. Warning: Permanently added '172.16.1.105' (RSA) to the list of known hosts. Warning: Permanently added '172.16.1.103' (RSA) to the list of known hosts. Sat May 12 14:30:06 2018 - [debug] ok. Sat May 12 14:30:06 2018 - [debug] Connecting via SSH from [email protected](172.16.1.105:22) to [email protected](172.16.1.104:22).. Sat May 12 14:30:06 2018 - [debug] ok. Sat May 12 14:30:06 2018 - [info] All SSH connection tests passed successfully.
檢查整個複製環境狀況
所有MHA node執行
[root@master1 ~]# ln -s /application/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog [root@master1 ~]# ln -s /application/mysql/bin/mysql /usr/local/bin/mysql [root@master1 ~]#
[root@manager ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf ......................................... 172.16.1.104(172.16.1.104:3306) (current master) +--172.16.1.105(172.16.1.105:3306) +--172.16.1.103(172.16.1.103:3306) Tue May 29 23:24:13 2018 - [info] Checking replication health on 172.16.1.105.. Tue May 29 23:24:13 2018 - [info] ok. Tue May 29 23:24:13 2018 - [info] Checking replication health on 172.16.1.103.. Tue May 29 23:24:13 2018 - [info] ok. Tue May 29 23:24:13 2018 - [info] Checking master_ip_failover_script status: Tue May 29 23:24:13 2018 - [info] /usr/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=172.16.1.104 --orig_master_ip=172.16.1.104 --orig_master_port=3306 Checking the Status of the script.. OK Tue May 29 23:24:13 2018 - [info] OK. Tue May 29 23:24:13 2018 - [warning] shutdown_script is not defined. Tue May 29 23:24:13 2018 - [info] Got exit code 0 (Not master dead). MySQL Replication Health is OK.
使用daemontools結合腳本來管理masterha_manager
cd /application/tools wget http://cr.yp.to/daemontools/daemontools-0.76.tar.gz tar xvzf daemontools-0.76.tar.gz cd admin/daemontools-0.76 vim src/conf-cc gcc -O2 -Wimplicit -Wunused -Wcomment -Wchar-subscripts -Wuninitialized -Wshadow -Wcast-qual -Wcast-align -Wwrite-strings -include /usr/include/errno.h This will be used to compile .c files. ./package/install mkdir /service/masterha_app1/ cd /service/masterha_app1/ vim run #!/bin/sh exec nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover >> /var/log/masterha/app1/manager.log chmod 755 /service/masterha_app1/run ln -s /application/tools/admin/daemontools/command/svscanboot /usr/bin echo "#MHA-manage" >> /etc/rc.local echo "/usr/local/bin/supervise /service/masterha_app1/&" >> /etc/rc.local 啓動MHA-manage svc -u /service/masterha_app1 關閉MHA-manage svc -d /service/masterha_app1
檢查MHA Manager的狀態
masterha_check_status --conf=/etc/masterha/app1.cnf app1 (pid:1090) is running(0:PING_OK), master:172.16.1.103
模擬主庫(172.16.1.103)發生故障，進行自動failover操作。
/etc/init.d/mysql stop Shutting down MySQL.................. SUCCESS!
檢查MHA Manager的狀態
masterha_check_status --conf=/etc/masterha/app1.cnf app1 (pid:1098) is running(0:PING_OK), master:172.16.1.104
郵箱中收到郵件
故障恢復把當即master作爲新master備選加入集羣
恢復步驟
(1)在現在的master或者slave使用mysqldump將數據備份，加--master-data=2 -A參數
(2)將備份數來的數據在服務器A上進行恢復，完成後執行flush privileges刷新權限
(3)完成後配置GTID的change master操作，start slave
(4)將主機的信息添加到mha的配置文件中，以便mha manager檢測到新的節點主機
(5)使用mha的測試命令進行測試,成功則啓動mha程序即可
腳本實現
recover.sh
id=`ifconfig eth0 | awk -F "[ :]+" 'NR==2 {print $4}'`
MHA_manager=172.16.1.109
if [ $# -eq 0 ]
then
echo "usage: $0 宕機master—ip 新master-ip slave-ip"
exit 0
fi
if [ `netstat -lntp | grep 3306 | wc -l` -eq 0 ]
then
echo "請確定mysql是否能正常啓動"
exit 1
fi
echo "relay_log 定時任務修改"
if [ `crontab -l | grep purge_relay_logs | wc -l` -eq 1 ]
then
echo "定時任務無需修改"
else
echo '0 5 * * * /usr/bin/purge_relay_logs --user=root --password=123456 --disable_relay_log_purge >> /application/mysql/log/mysql-del-relay.log 2>&1' >> /var/spool/cron/root
fi
echo "把原master作爲新master的備選"
relay=`ssh root@$2 "crontab -l | grep purge_relay_logs | wc -l"`
if [ $relay -eq 1 ]
then
ssh root@$2 "sed -i '/purge_relay_logs*/d' /var/spool/cron/root"
else
echo "$2上rerelay_log定時任務無需修改"
fi
mysqldump -h $3 -uroot -p123456 --master-data=2 --single-transaction --default-character-set=utf8mb4 -R --triggers -A > /tmp/new_master_data.sql >/dev/null 2>&1
mysql -uroot -p123456 </tmp/new_master_data.sql >/dev/null 2>&1
changmaster="CHANGE MASTER TO MASTER_HOST='"$2"',MASTER_USER='"mysql01"',MASTER_PASSWORD='"mysql01"',MASTER_AUTO_POSITION=1;"
mysql -uroot -p123456 -e "`echo $changmaster`"
mysql -uroot -p123456 -e "start slave;" >/dev/null 2>&1
echo "把原master作爲新master的備選加入集羣"
ssh root@$MHA_manager "sed -i '/^check_repl_delay*/d' /etc/masterha/app1.cnf"
ssh root@$MHA_manager "sed -i '/^secondary_check_script*/d' /etc/masterha/app1.cnf"
ssh root@$MHA_manager "sed -i '/^candidate_master*/d' /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo " " >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "secondary_check_script=/usr/bin/masterha_secondary_check -s $1 --user=root --master_host=$2 --master_ip=$2 --master_port=3306" >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo " " >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "[server$id]" >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "candidate_master=1" >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "hostname=$1" >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "check_repl_delay=0" >> /etc/masterha/app1.cnf"
ssh root@$MHA_manager "echo "port=3306" >> /etc/masterha/app1.cnf"執行腳本測試
[root@master1 ~]# /etc/init.d/mysql start [root@master1 ~]# sh /server/scripts/recover.sh 172.16.1.103 172.16.1.104 172.16.1.105 relay_log 定時任務修改 定時任務無需修改 把原master作爲新master的備選 172.16.1.104上rerelay_log定時任務無需修改 mysql: [Warning] Using a password on the command line interface can be insecure. 把原master作爲新master的備選加入集羣
檢查MHA Manager的狀態
masterha_check_status --conf=/etc/masterha/app1.cnf app1 (pid:1098) is running(0:PING_OK), master:172.16.1.104 masterha_check_repl --conf=/etc/masterha/app1.cnf 172.16.1.104(172.16.1.104:3306) (current master) +--172.16.1.105(172.16.1.105:3306) +--172.16.1.103(172.16.1.103:3306) .............................. MySQL Replication Health is OK.