MHA手动故障转移
MHA提供了3种方式用于实现故障转移,分别自动故障转移,需要启用MHA监控;在无监控的情况下的手动故障转移以及基于在线手动切换。三种方式可以应对MySQL主从故障的任意场景。本文主要描述在无监控的情形是手动实现故障转移。供大家参考。
有关MHA的其他两种切换方式,可以参考:
1、手动故障转移的特点
2、masterha_master_switch切换的几个参数
3、演示手动故障转移
###master开启VIP
###检测MHA监控是否运行,如果已启动,可以使用masterha_check_stop先停止
###模拟从库滞后
###主库上插入新记录
###模拟master异常宕机
###开始手工故障转移
IN SCRIPT TEST====/sbin/ifconfig eth0:0 down==/sbin/ifconfig eth0:0 192.168.1.13/24===
Disabling the VIP on old master: vdbsrv1
To:
Starting master switch from vdbsrv1(192.168.1.6:3306) to vdbsrv3(192.168.1.8:3306)? (yes/NO): yes
IN SCRIPT TEST====/sbin/ifconfig eth0:0 down==/sbin/ifconfig eth0:0 192.168.1.13/24===
Enabling the VIP - 192.168.1.13/24 on the new master - vdbsrv3
----- Failover Report -----
app1: MySQL Master failover vdbsrv1(192.168.1.6:3306) to vdbsrv3(192.168.1.8:3306) succeeded
Master vdbsrv1(192.168.1.6:3306) is down!
Check MHA Manager logs at vdbsrv4 for details.
Started manual(interactive) failover.