MySQL高可用方案MHA自动Failover与手动Failover的实践及原理
集群信息
角色 IP地址 ServerID 类型
Master 192.168.244.10 1 写入
Candicate master 192.168.244.20 2 读
Slave 192.168.244.30 3 读
Monitor host 192.168.244.40 监控集群组
MHA具体的搭建步骤和原理，可参考另外一篇博客：
自动Failover
为了通过MHA的日志清晰判断MHA自动Failover的实现原理，需模拟如下场景：
当主库发生故障时，master中还有一部分binlog日志没有传输到Candicate master和Slave上，且Slave上的二进制日志多于Candicate master上。
尝试了几种方案，总算如愿以偿。
方案一：
1. 关闭Candicate master和Slave的主从复制。
2. 通过存储过程生成测试数据
3. 开启Candicate master和Slave的主从复制并kill掉master的mysqld进程，模拟主库发生故障，进行自动failover操作
为此，还特意写了个脚本，可惜的是，效果并不理想，在自动Failover的过程中，显示MHA Manager到master的“SSH is NOT reachable”。
方案二：
通过tc命令对Candicate master和Slave的网卡分别设置不同的传输速率，确保发送到Candicate master的日志量小于Slave上的。
很可惜，效果同方案一一样。
方案三：
在主从复制中，直接关闭master的mysqld数据库。
但是，通过这样方式，并不会实现Slave上的二进制日志多于Candicate master的效果。
方案四：
通过截取relay log，在关掉slave的情况下，修改master.info和relay-log.info的位置点来人为制造Candicate master的日志量小于Slave的。
事后想想，其实这样的方法就等同于先关闭Candicate master的主从复制，再在master上执行一段操作，再关闭slave上的主从复制，再在master上执行一段操作。
这样不就实现了master的binlog > slave 的relay log > Candicate master的relay log。
方案四总算如愿以偿
下面通过方案四看看MHA的实现原理
1. 创建测试表，并插入测试数据
mysql> create table sbtest.b(id int,name varchar(10));
Query OK, 0 rows affected (0.12 sec) mysql> insert into sbtest.b values(1,'a');
Query OK, 1 row affected (0.00 sec) mysql> insert into sbtest.b values(2,'b');
Query OK, 1 row affected (0.01 sec) mysql> insert into sbtest.b values(3,'c');
Query OK, 1 row affected (0.00 sec) mysql> insert into sbtest.b values(4,'d');
Query OK, 1 row affected (0.00 sec) mysql> insert into sbtest.b values(5,'e');
Query OK, 1 row affected (0.01 sec)
2. 分别查看master上binlog的内容，slave上relay log的内容
Master
mysql> show binlog events;
+------------------+------+-------------+-----------+-------------+------------------------------------------------+
| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |
+------------------+------+-------------+-----------+-------------+------------------------------------------------+
| mysql-bin.000001 | 4 | Format_desc | 1 | 120 | Server ver: 5.6.31-log, Binlog ver: 4 |
| mysql-bin.000001 | 120 | Query | 1 | 238 | create table sbtest.b(id int,name varchar(10)) |
| mysql-bin.000001 | 238 | Query | 1 | 315 | BEGIN |
| mysql-bin.000001 | 315 | Query | 1 | 421 | insert into sbtest.b values(1,'a') |
| mysql-bin.000001 | 421 | Xid | 1 | 452 | COMMIT /* xid=102 */ |
| mysql-bin.000001 | 452 | Query | 1 | 529 | BEGIN |
| mysql-bin.000001 | 529 | Query | 1 | 635 | insert into sbtest.b values(2,'b') |
| mysql-bin.000001 | 635 | Xid | 1 | 666 | COMMIT /* xid=103 */ |
| mysql-bin.000001 | 666 | Query | 1 | 743 | BEGIN |
| mysql-bin.000001 | 743 | Query | 1 | 849 | insert into sbtest.b values(3,'c') |
| mysql-bin.000001 | 849 | Xid | 1 | 880 | COMMIT /* xid=104 */ |
| mysql-bin.000001 | 880 | Query | 1 | 957 | BEGIN |
| mysql-bin.000001 | 957 | Query | 1 | 1063 | insert into sbtest.b values(4,'d') |
| mysql-bin.000001 | 1063 | Xid | 1 | 1094 | COMMIT /* xid=105 */ |
| mysql-bin.000001 | 1094 | Query | 1 | 1171 | BEGIN |
| mysql-bin.000001 | 1171 | Query | 1 | 1277 | insert into sbtest.b values(5,'e') |
| mysql-bin.000001 | 1277 | Xid | 1 | 1308 | COMMIT /* xid=106 */ |
+------------------+------+-------------+-----------+-------------+------------------------------------------------+
17 rows in set (0.01 sec)
Slave
mysql> show relaylog events in 'mysqld-relay-bin.000002';
+-------------------------+------+-------------+-----------+-------------+------------------------------------------------+
| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |
+-------------------------+------+-------------+-----------+-------------+------------------------------------------------+
| mysqld-relay-bin.000002 | 4 | Format_desc | 2 | 120 | Server ver: 5.6.31-log, Binlog ver: 4 |
| mysqld-relay-bin.000002 | 120 | Rotate | 1 | 0 | mysql-bin.000001;pos=120 |
| mysqld-relay-bin.000002 | 167 | Format_desc | 1 | 0 | Server ver: 5.6.31-log, Binlog ver: 4 |
| mysqld-relay-bin.000002 | 283 | Query | 1 | 238 | create table sbtest.b(id int,name varchar(10)) |
| mysqld-relay-bin.000002 | 401 | Query | 1 | 315 | BEGIN |
| mysqld-relay-bin.000002 | 478 | Query | 1 | 421 | insert into sbtest.b values(1,'a') |
| mysqld-relay-bin.000002 | 584 | Xid | 1 | 452 | COMMIT /* xid=102 */ |
| mysqld-relay-bin.000002 | 615 | Query | 1 | 529 | BEGIN |
| mysqld-relay-bin.000002 | 692 | Query | 1 | 635 | insert into sbtest.b values(2,'b') |
| mysqld-relay-bin.000002 | 798 | Xid | 1 | 666 | COMMIT /* xid=103 */ |
| mysqld-relay-bin.000002 | 829 | Query | 1 | 743 | BEGIN |
| mysqld-relay-bin.000002 | 906 | Query | 1 | 849 | insert into sbtest.b values(3,'c') |
| mysqld-relay-bin.000002 | 1012 | Xid | 1 | 880 | COMMIT /* xid=104 */ |
| mysqld-relay-bin.000002 | 1043 | Query | 1 | 957 | BEGIN |
| mysqld-relay-bin.000002 | 1120 | Query | 1 | 1063 | insert into sbtest.b values(4,'d') |
| mysqld-relay-bin.000002 | 1226 | Xid | 1 | 1094 | COMMIT /* xid=105 */ |
| mysqld-relay-bin.000002 | 1257 | Query | 1 | 1171 | BEGIN |
| mysqld-relay-bin.000002 | 1334 | Query | 1 | 1277 | insert into sbtest.b values(5,'e') |
| mysqld-relay-bin.000002 | 1440 | Xid | 1 | 1308 | COMMIT /* xid=106 */ |
+-------------------------+------+-------------+-----------+-------------+------------------------------------------------+
19 rows in set (0.00 sec)
通过对比master中的binlog event，可以看到show relaylog events中的End_log_pos实际上指的是对应的二进制事件在binlog的位置。
再来查看Candicate master中对应的relay log的内容
[root@node2 mysql]# mysqlbinlog mysqld-relay-bin.000002
[root@node2 mysql]# mysqlbinlog mysqld-relay-bin.
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at
# :: server id end_log_pos CRC32 0x4faba9ae Start: binlog v , server v 5.6.-log created ::
BINLOG '
dU8lWQ8CAAAAdAAAAHgAAABAAAQANS42LjMxLWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAa6p
q08=
'/*!*/;
# at
# :: server id end_log_pos CRC32 0x74c6d70c Rotate to mysql-bin. pos:
# at
# :: server id end_log_pos CRC32 0xed2672eb Start: binlog v , server v 5.6.-log created ::
BINLOG '
RU8lWQ8BAAAAdAAAAAAAAAAAAAQANS42LjMxLWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAXAAEGggAAAAICAgCAAAACgoKGRkAAety
Ju0=
'/*!*/;
# at
# :: server id end_log_pos CRC32 0xdd48c118 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
SET @@session.pseudo_thread_id=/*!*/;
SET @@session.foreign_key_checks=, @@session.sql_auto_is_null=, @@session.unique_checks=, @@session.autocommit=/*!*/;
SET @@session.sql_mode=/*!*/;
SET @@session.auto_increment_increment=, @@session.auto_increment_offset=/*!*/;
/*!\C utf8 *//*!*/;
SET @@session.character_set_client=,@@session.collation_connection=,@@session.collation_server=/*!*/;
SET @@session.lc_time_names=/*!*/;
SET @@session.collation_database=DEFAULT/*!*/;
create table sbtest.b(id int,name varchar())
/*!*/;
# at
# :: server id end_log_pos CRC32 0xae393750 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
BEGIN
/*!*/;
# at
# :: server id end_log_pos CRC32 0x28a781ae Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
insert into sbtest.b values(,'a')
/*!*/;
# at
# :: server id end_log_pos CRC32 0x680f1bfe Xid =
COMMIT/*!*/;
# at
# :: server id end_log_pos CRC32 0x6a1aae7e Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
BEGIN
/*!*/;
# at
# :: server id end_log_pos CRC32 0x117786ca Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
insert into sbtest.b values(,'b')
/*!*/;
# at
# :: server id end_log_pos CRC32 0xa8400ec6 Xid =
COMMIT/*!*/;
# at
# :: server id end_log_pos CRC32 0x24f9a1d2 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
BEGIN
/*!*/;
# at
# :: server id end_log_pos CRC32 0x56fa9e89 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
insert into sbtest.b values(,'c')
/*!*/;
# at
# :: server id end_log_pos CRC32 0x2ac656d4 Xid =
COMMIT/*!*/;
# at
# :: server id end_log_pos CRC32 0x73a903bf Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
BEGIN
/*!*/;
# at
# :: server id end_log_pos CRC32 0x171b9b27 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
insert into sbtest.b values(,'d')
/*!*/;
# at
# :: server id end_log_pos CRC32 0x47d6fe57 Xid =
COMMIT/*!*/;
# at
# :: server id end_log_pos CRC32 0x2d37da37 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
BEGIN
/*!*/;
# at
# :: server id end_log_pos CRC32 0xd2201fa2 Query thread_id= exec_time= error_code=
SET TIMESTAMP=/*!*/;
insert into sbtest.b values(,'e')
/*!*/;
# at
# :: server id end_log_pos CRC32 0xac1b464e Xid =
COMMIT/*!*/;
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;
mysql中binlog有个有意思的地方是，位置点其实是也是字节的大小。
譬如，上面这个relay log中，最后一个位点是# at 1440，算上最后一个commit操作需占用31个字节，所以整个文件的大小是1471，与实际大小吻合。
[root@node2 mysql]# ll mysqld-relay-bin.
-rw-rw---- mysql mysql May : mysqld-relay-bin.
3. 通过show slave status查看io thread和sql thread的位置信息
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.244.10
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000001
Read_Master_Log_Pos: 1308
Relay_Log_File: mysqld-relay-bin.000002
Relay_Log_Pos: 1471
Relay_Master_Log_File: mysql-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: 1308
Relay_Log_Space: 1645
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:
Master_Server_Id: 1
Master_UUID: 2a6365e0-1d05-11e7-956d-000c29c64704
Master_Info_File: /var/lib/mysql/master.info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it
Master_Retry_Count: 86400
Master_Bind:
Last_IO_Error_Timestamp:
Last_SQL_Error_Timestamp:
Master_SSL_Crl:
Master_SSL_Crlpath:
Retrieved_Gtid_Set:
Executed_Gtid_Set:
Auto_Position: 0
1 row in set (0.00 sec)
待会儿需要修改上面Master_Log_File,Read_Master_Log_Pos,Relay_Log_File,Relay_Log_Pos,Relay_Master_Log_File,Exec_Master_Log_Pos的值。
虽然这几个参数的值与master.info和relay-log.info文件是相对应的，
但通过修改master.info和relay-log.info的值，并重启slave，并不会将上述几个参数值修改。
上述几个参数是保存到内存中的，唯一可行的方案是首先关闭slave实例，再修改master.info和relay-log.info文件，然后重新启动mysql实例。
4. 关闭Candicate master实例，剪裁relay log，修改master.info和relay-log.info文件。
关闭实例
[root@node2 mysql]# service mysqld stop
剪裁relay log
这里，写了个python脚本实现该功能
#!/usr/bin/python
f1 = open('mysqld-relay-bin.000002','r')
f2 = open('tmp_relay_bin','w+')
size1=f1.read(615)
f2.write(size1)
f1.seek(1471)
size2=f1.read()
f2.write(size2)
f1.close()
f2.close()
在上述脚本size1中，615对应的是insert into sbtest.b values(1,'a')这条记录
[root@node2 mysql]# python 1.py
[root@node2 mysql]# mv tmp_relay_bin mysqld-relay-bin.000002
修改master.info的内容
主要是修改第三行
mysql-bin.
修改为
mysql-bin.
修改relay-log.info的内容
原文件如下：
./mysqld-relay-bin. mysql-bin.
修改为：
./mysqld-relay-bin. mysql-bin.
启动slave，注意，配置文件中必须设置skip-slave-start，不然它自动开启主从复制。
[root@node2 mysql]# service mysqld start
5. 对于slave，同样如此处理，只不过relay log的位置点要靠后些
#!/usr/bin/python
f1 = open('mysqld-relay-bin.000002','r')
f2 = open('tmp_relay_bin','w+')
size1=f1.read(1043)
f2.write(size1)
f1.seek(1471)
size2=f1.read()
f2.write(size2)
f1.close()
f2.close()
1043对应的是insert into sbtest.b values(3,'c')这条记录
修改master.info的内容
23
mysql-bin.000001
880
修改relay-log.info的内容
7
./mysqld-relay-bin.000002
1043
mysql-bin.000001
880
0
0
1
6. 开启MHA监控
# nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null >
/masterha/app1/manager.log 2>&1 &
# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:1615) is running(0:PING_OK), master:192.168.244.10
7. 关闭master实例
# service mysqld stop
8. 查看MHA切换日志，了解整个切换过程。
该日志的时间点与上面relay log的时间点并不吻合，原因在于这个反复测试了很多次。
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [info] Executing secondary network check script: /usr/local/bin/masterha_secondary_check -s 192.168.244.20 -s 192.168.244.30 --user=root --master_host=192.168.244.10 --master_ip=192.168.244.10 --master_port= --user=root --master_host=192.168.244.10 --master_ip=192.168.244.10 --master_port= --master_user=monitor --master_password=monitor123 --ping_type=SELECT
Sun May :: - [info] Executing SSH check script: save_binary_logs --command=test --start_pos= --binlog_dir=/var/lib/mysql --output_file=/tmp/save_binary_logs_test --manager_version=0.56 --binlog_prefix=mysql-bin
Monitoring server 192.168.244.20 is reachable, Master is not reachable from 192.168.244.20. OK.
Sun May :: - [info] HealthCheck: SSH to 192.168.244.10 is reachable.
Monitoring server 192.168.244.30 is reachable, Master is not reachable from 192.168.244.30. OK. -- 当monitor检测到master mysqld不可用的时候，即根据masterha_secondary_check脚本从Candicate master和Slave上判断master mysqld的可用性，
根据上面的显示信息，通过192.168.244.20和192.168.244.30也判断到master mysqld不可用。 如果任意一个slave判断到master mysqld可用，则输出的信息如下：
# /usr/local/bin/masterha_secondary_check -s 192.168.244.20 -s 192.168.244.30 --user=root --master_host=192.168.244.10 --master_ip=192.168.244.10 --master_port= Master is reachable from 192.168.244.20! Sun May :: - [info] Master is not reachable from all other monitoring servers. Failover should start.
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [warning] Master is not reachable from health checker!
Sun May :: - [warning] Master 192.168.244.10(192.168.244.10:) is not reachable!
Sun May :: - [warning] SSH is reachable. -- 一共判断了4次，均判断master mysqld不可用，但是master主机通过ssh还是能登录上去。
如果这里显示的是SSH is NOT reachable，则代表master主机也已经宕机了，
刚开始还以为是通过ssh来判断主机是否宕机，但在之前的测试方案中（具体可见文末），master并没有宕机，这里却显示SSH is NOT reachable.
通过上面的输出才知道是通过save_binary_logs脚本来判断ssh可用性的。 Sun May :: - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..
Sun May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sun May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sun May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sun May :: - [warning] SQL Thread is stopped(no error) on 192.168.244.20(192.168.244.20:)
Sun May :: - [warning] SQL Thread is stopped(no error) on 192.168.244.30(192.168.244.30:)
Sun May :: - [info] GTID failover mode =
Sun May :: - [info] Dead Servers:
Sun May :: - [info] 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Alive Servers:
Sun May :: - [info] 192.168.244.20(192.168.244.20:)
Sun May :: - [info] 192.168.244.30(192.168.244.30:)
Sun May :: - [info] Alive Slaves:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Checking slave configurations..
Sun May :: - [info] Checking replication filtering settings..
Sun May :: - [info] Replication filtering check ok.
Sun May :: - [info] Master is down!
Sun May :: - [info] Terminating monitoring script.
Sun May :: - [info] Got exit code (Master dead).
Sun May :: - [info] MHA::MasterFailover version 0.56.
Sun May :: - [info] Starting master failover. -- 读取MHA的配置文件，检查slave的相关配置，比如read_only参数，是否设置了复制的过滤规则
从上面的输出中可以看出，SQL Thread正常停止了并不影响MHA的切换。 Sun May :: - [info]
Sun May :: - [info] * Phase : Configuration Check Phase..
Sun May :: - [info]
Sun May :: - [warning] SQL Thread is stopped(no error) on 192.168.244.20(192.168.244.20:)
Sun May :: - [warning] SQL Thread is stopped(no error) on 192.168.244.30(192.168.244.30:)
Sun May :: - [info] GTID failover mode =
Sun May :: - [info] Dead Servers:
Sun May :: - [info] 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Checking master reachability via MySQL(double check)...
Sun May :: - [info] ok.
Sun May :: - [info] Alive Servers:
Sun May :: - [info] 192.168.244.20(192.168.244.20:)
Sun May :: - [info] 192.168.244.30(192.168.244.30:)
Sun May :: - [info] Alive Slaves:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Starting SQL thread on 192.168.244.20(192.168.244.20:) ..
Sun May :: - [info] done.
Sun May :: - [info] Starting SQL thread on 192.168.244.30(192.168.244.30:) ..
Sun May :: - [info] done.
Sun May :: - [info] Starting Non-GTID based failover.
Sun May :: - [info]
Sun May :: - [info] ** Phase : Configuration Check Phase completed. -- 第一阶段，检查了MHA的配置信息，并再次判断了master的可用性。
第二阶段，关闭dead master。
包括执行摘除master上的vip，同时执行shutdown_script脚本，因为该脚本在配置文件中没有定义，故跳过。 Sun May :: - [info]
Sun May :: - [info] * Phase : Dead Master Shutdown Phase..
Sun May :: - [info]
Sun May :: - [info] Forcing shutdown so that applications never connect to the current master..
Sun May :: - [info] Executing master IP deactivation script:
Sun May :: - [info] /usr/local/bin/master_ip_failover --orig_master_host=192.168.244.10 --orig_master_ip=192.168.244.10 --orig_master_port= --command=stopssh --ssh_user=root
Disabling the VIP an old master: 192.168.244.10
SIOCSIFFLAGS: Cannot assign requested address
Sun May :: - [info] done.
Sun May :: - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Sun May :: - [info] * Phase : Dead Master Shutdown Phase completed.
Sun May :: - [info] -- 第三阶段
3.1 判断哪个slave的二进制日志是最新的。
通过下面的输出可以看出，所有的slave中，最新的二进制日志位置是mysql-bin.:（通过show slave status中的Master_Log_File, Read_Master_Log_Pos得到）
最旧的二进制日志位置是mysql-bin.: Sun May :: - [info] * Phase : Master Recovery Phase..
Sun May :: - [info]
Sun May :: - [info] * Phase 3.1: Getting Latest Slaves Phase..
Sun May :: - [info]
Sun May :: - [info] The latest binary log file/position on all slaves is mysql-bin.:
Sun May :: - [info] Latest slaves (Slaves that received relay log files to the latest):
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] The oldest binary log file/position on all slaves is mysql-bin.:
Sun May :: - [info] Oldest slaves:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] -- 3.2 保存master的binlog
注意，上面已经判断到slave中最新二进制日志是mysql-bin.:，所以它把该位置后所有二进制日志都拼接起来，并scp到monitor的/masterha/app1目录下。 Sun May :: - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Sun May :: - [info]
Sun May :: - [info] Fetching dead master's binary logs..
Sun May :: - [info] Executing command on the dead master 192.168.244.10(192.168.244.10:): save_binary_logs --command=save --start_file=mysql-bin. --start_pos= --binlog_dir=/var/lib/mysql --output_file=/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog --handle_raw_binlog= --disable_log_bin= --manager_version=0.56
Creating /tmp if not exists.. ok.
Concat binary/relay logs from mysql-bin. pos to mysql-bin. EOF into /tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog ..
Binlog Checksum enabled
Dumping binlog format description event, from position to .. ok.
Dumping effective binlog data from /var/lib/mysql/mysql-bin. position to tail().. ok.
Binlog Checksum enabled
Concat succeeded.
Sun May :: - [info] scp from root@192.168.244.10:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog to local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog succeeded.
Sun May :: - [info] HealthCheck: SSH to 192.168.244.20 is reachable.
Sun May :: - [info] HealthCheck: SSH to 192.168.244.30 is reachable.
Sun May :: - [info] -- 3.3 选新主阶段
首先判断最新的slave中是否包括最旧的二进制日志（mysql-bin.:）以后的relay log。
接着选新主，
因为192.168.244.20中设置了candidate_master设置了，所以192.168.244.20被指定为新主。 Sun May :: - [info] * Phase 3.3: Determining New Master Phase..
Sun May :: - [info]
Sun May :: - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Sun May :: - [info] Checking whether 192.168.244.30 has relay logs from the oldest position..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=find --latest_mlf=mysql-bin. --latest_rmlp= --target_mlf=mysql-bin. --target_rmlp= --server_id= --workdir=/tmp --timestamp= --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ :
Opening /var/lib/mysql/relay-log.info ... ok.
Relay log found at /var/lib/mysql, up to mysqld-relay-bin.
Fast relay log position search failed. Reading relay logs to find..
Reading mysqld-relay-bin.
Binlog Checksum enabled
Reading mysqld-relay-bin.
Binlog Checksum enabled
Master Version is 5.6.-log
Binlog Checksum enabled
mysqld-relay-bin. contains master mysql-bin. from position
Target relay log FOUND!
Sun May :: - [info] OK. 192.168.244.30 has all relay logs.
Sun May :: - [info] Searching new master from slaves..
Sun May :: - [info] Candidate masters from the configuration file:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] Non-candidate masters:
Sun May :: - [info] Searching from candidate_master slaves which have received the latest relay log events..
Sun May :: - [info] Not found.
Sun May :: - [info] Searching from all candidate_master slaves..
Sun May :: - [info] New master is 192.168.244.20(192.168.244.20:)
Sun May :: - [info] Starting master failover..
Sun May :: - [info]
From:
192.168.244.10(192.168.244.10:) (current master)
+--192.168.244.20(192.168.244.20:)
+--192.168.244.30(192.168.244.30:) To:
192.168.244.20(192.168.244.20:) (new master)
+--192.168.244.30(192.168.244.30:)
Sun May :: - [info] -- 3.3 获取新主所需的差异二进制日志，包括两部分
> 新主和最新的slave之间差异的relay log
> 保存在MHA Manager上的最新的slave和原master之前差异的binlog
其中，差异的relay log通过如下方式获取：
ssh到192.168.244.30上，执行apply_diff_relay_logs获取差异的relay log。将差异的relay log scp到192.168.244.。 Sun May :: - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Sun May :: - [info]
Sun May :: - [info] Server 192.168.244.20 received relay logs up to: mysql-bin.:
Sun May :: - [info] Need to get diffs from the latest slave(192.168.244.30) up to: mysql-bin.: (using the latest slave's relay logs)
Sun May :: - [info] Connecting to the latest slave host 192.168.244.30, generating diff relay log files..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=generate_and_send --scp_user=root --scp_host=192.168.244.20 --latest_mlf=mysql-bin. --latest_rmlp= --target_mlf=mysql-bin. --target_rmlp= --server_id= --diff_file_readtolatest=/tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog --workdir=/tmp --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/
Sun May :: - [info]
Opening /var/lib/mysql/relay-log.info ... ok.
Relay log found at /var/lib/mysql, up to mysqld-relay-bin.
Fast relay log position search failed. Reading relay logs to find..
Reading mysqld-relay-bin.
Binlog Checksum enabled
Reading mysqld-relay-bin.
Binlog Checksum enabled
Master Version is 5.6.-log
Binlog Checksum enabled
mysqld-relay-bin. contains master mysql-bin. from position
Target relay log file/position found. start_file:mysqld-relay-bin., start_pos:.
Concat binary/relay logs from mysqld-relay-bin. pos to mysqld-relay-bin. EOF into /tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog ..
Binlog Checksum enabled
Binlog Checksum enabled
Dumping binlog format description event, from position to .. ok.
Dumping effective binlog data from /var/lib/mysql/mysqld-relay-bin. position to tail().. ok.
Dumping binlog head events (rotate events), skipping format description events from /var/lib/mysql/mysqld-relay-bin... Binlog Checksum enabled
dumped up to pos . ok.
No need to dump effective binlog data from /var/lib/mysql/mysqld-relay-bin. (pos starts , filesize ). Skipping.
Binlog Checksum enabled
Binlog Checksum enabled
Concat succeeded.
Generating diff relay log succeeded. Saved at /tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog .
scp node3:/tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog to root@192.168.244.20() succeeded.
Sun May :: - [info] Generating diff files succeeded.
Sun May :: - [info] Sending binlog..
Sun May :: - [info] scp from local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog to root@192.168.244.20:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog succeeded.
Sun May :: - [info] -- 3.4 应用从master保存的二进制日志事件
首先，等原来的所有的relay log都应用完。
其次，再通过apply_diff_relay_logs应用差异的relay log，及差异的binlog。
应用完毕后，得到新的master binlog的文件和位置，其它slave可根据该文件和位置来建立主从复制关系。
第三，执行master_ip_failover脚本，执行如下操作
> 将新主的read_only设置为0
> 启动vip Sun May :: - [info] * Phase 3.4: Master Log Apply Phase..
Sun May :: - [info]
Sun May :: - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Sun May :: - [info] Starting recovery on 192.168.244.20(192.168.244.20:)..
Sun May :: - [info] Generating diffs succeeded.
Sun May :: - [info] Waiting until all relay logs are applied.
Sun May :: - [info] done.
Sun May :: - [info] Getting slave status..
Sun May :: - [info] This slave(192.168.244.20)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000001:452). No need to recover from Exec_Master_Log_Pos.
Sun May :: - [info] Connecting to the target slave host 192.168.244.20, running recover script..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='monitor' --slave_host=192.168.244.20 --slave_ip=192.168.244.20 --slave_port= --apply_files=/tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog,/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog --workdir=/tmp --target_version=5.6.-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --slave_pass=xxx
Sun May :: - [info]
Concat all apply files to /tmp/total_binlog_for_192.168.244.20_3306..binlog ..
Copying the first binlog file /tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog to /tmp/total_binlog_for_192.168.244.20_3306..binlog.. ok.
Dumping binlog head events (rotate events), skipping format description events from /tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog.. Binlog Checksum enabled
dumped up to pos . ok.
/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog has effective binlog events from pos .
Dumping effective binlog data from /tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog position to tail().. ok.
Concat succeeded.
All apply target binary logs are concatinated at /tmp/total_binlog_for_192.168.244.20_3306..binlog .
MySQL client version is 5.6.. Using --binary-mode.
Applying differential binary/relay log files /tmp/relay_from_read_to_latest_192.168.244.20_3306_20170521205050.binlog,/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog on 192.168.244.20:. This may take long time...
Applying log files succeeded.
Sun May :: - [info] All relay logs were successfully applied.
Sun May :: - [info] Getting new master's binlog name and position..
Sun May :: - [info] mysql-bin.:
Sun May :: - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.244.20', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Sun May :: - [info] Executing master IP activate script:
Sun May :: - [info] /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.244.10 --orig_master_ip=192.168.244.10 --orig_master_port= --new_master_host=192.168.244.20 --new_master_ip=192.168.244.20 --new_master_port= --new_master_user='monitor' --new_master_password='monitor123'
Set read_only= on the new master.
Enabling the VIP 192.168.244.188 on the new master: 192.168.244.20
Sun May :: - [info] OK.
Sun May :: - [info] ** Finished master recovery successfully.
Sun May :: - [info] * Phase : Master Recovery Phase completed. -- 第四阶段 slave恢复阶段
-- 4.1 因为192.168.244.30拥有最新的relay log，所以也没必要获取差异的relay log
-- 4.2 开始slave的恢复阶段
> 将monitor上保存的master上的差异的二进制日志scp到slave上。
> 应用差异日志。
> 清除原来的复制关系，并再次执行change master命令建立新的主从同步。
如果有多个slave，则该恢复过程是并行的。 Sun May :: - [info]
Sun May :: - [info] * Phase : Slaves Recovery Phase..
Sun May :: - [info]
Sun May :: - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Sun May :: - [info]
Sun May :: - [info] -- Slave diff file generation on host 192.168.244.30(192.168.244.30:) started, pid: . Check tmp log /masterha/app1/192.168..30_3306_20170521205050.log if it takes time..
Sun May :: - [info]
Sun May :: - [info] Log messages from 192.168.244.30 ...
Sun May :: - [info]
Sun May :: - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Sun May :: - [info] End of log messages from 192.168.244.30.
Sun May :: - [info] -- 192.168.244.30(192.168.244.30:) has the latest relay log events.
Sun May :: - [info] Generating relay diff files from the latest slave succeeded.
Sun May :: - [info]
Sun May :: - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Sun May :: - [info]
Sun May :: - [info] -- Slave recovery on host 192.168.244.30(192.168.244.30:) started, pid: . Check tmp log /masterha/app1/192.168..30_3306_20170521205050.log if it takes time..
Sun May :: - [info]
Sun May :: - [info] Log messages from 192.168.244.30 ...
Sun May :: - [info]
Sun May :: - [info] Sending binlog..
Sun May :: - [info] scp from local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog to root@192.168.244.30:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog succeeded.
Sun May :: - [info] Starting recovery on 192.168.244.30(192.168.244.30:)..
Sun May :: - [info] Generating diffs succeeded.
Sun May :: - [info] Waiting until all relay logs are applied.
Sun May :: - [info] done.
Sun May :: - [info] Getting slave status..
Sun May :: - [info] This slave(192.168.244.30)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000001:880). No need to recover from Exec_Master_Log_Pos.
Sun May :: - [info] Connecting to the target slave host 192.168.244.30, running recover script..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='monitor' --slave_host=192.168.244.30 --slave_ip=192.168.244.30 --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog --workdir=/tmp --target_version=5.6.-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --slave_pass=xxx
Sun May :: - [info]
MySQL client version is 5.6.. Using --binary-mode.
Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.244.10_3306_20170521205050.binlog on 192.168.244.30:. This may take long time...
Applying log files succeeded.
Sun May :: - [info] All relay logs were successfully applied.
Sun May :: - [info] Resetting slave 192.168.244.30(192.168.244.30:) and starting replication from the new master 192.168.244.20(192.168.244.20:)..
Sun May :: - [info] Executed CHANGE MASTER.
Sun May :: - [info] Slave started.
Sun May :: - [info] End of log messages from 192.168.244.30.
Sun May :: - [info] -- Slave recovery on host 192.168.244.30(192.168.244.30:) succeeded.
Sun May :: - [info] All new slave servers recovered successfully. -- 第五阶段 清理阶段
从MHA的配置文件中剔除server1的配置信息 Sun May :: - [info]
Sun May :: - [info] * Phase : New master cleanup phase..
Sun May :: - [info]
Sun May :: - [info] Resetting slave info on the new master..
Sun May :: - [info] 192.168.244.20: Resetting slave info succeeded.
Sun May :: - [info] Master failover to 192.168.244.20(192.168.244.20:) completed successfully.
Sun May :: - [info] Deleted server1 entry from /etc/masterha/app1.cnf .
Sun May :: - [info] -- 生成 Failover 报告，发送告警邮件 ----- Failover Report ----- app1: MySQL Master failover 192.168.244.10(192.168.244.10:) to 192.168.244.20(192.168.244.20:) succeeded Master 192.168.244.10(192.168.244.10:) is down! Check MHA Manager logs at node4:/masterha/app1/manager.log for details. Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.244.10(192.168.244.10:)
The latest slave 192.168.244.30(192.168.244.30:) has all relay logs for recovery.
Selected 192.168.244.20(192.168.244.20:) as a new master.
192.168.244.20(192.168.244.20:): OK: Applying all logs succeeded.
192.168.244.20(192.168.244.20:): OK: Activated master IP address.
192.168.244.30(192.168.244.30:): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.244.30(192.168.244.30:): OK: Applying all logs succeeded. Slave started, replicating from 192.168.244.20(192.168.244.20:)
192.168.244.20(192.168.244.20:): Resetting slave info succeeded.
Master failover to 192.168.244.20(192.168.244.20:) completed successfully.
Sun May :: - [info] Sending mail..
Unknown option: conf
从上面的日志输出可以看出整个MHA的切换过程
首先，MHA Manager检测到master不可用，则会通过另外两个slave检查master的可用性。一共检测4次。
同时判断MHA Manager到master的ssh可用性。
ssh可用性的判断结果影响后后续切换中的“Phase 3.2: Saving Dead Master's Binlog Phase”
Phase 1: Configuration Check Phase..
检查了MHA的配置信息，并再次判断了master的可用性。
Phase 2: Dead Master Shutdown Phase..
宕机的master处理阶段，包括摘除VIP，执行shutdown_script中定义的脚本。
Phase 3: Master Recovery Phase..
Phase 3.1: Getting Latest Slaves Phase..
判断哪个slave拥有最新的relay log（通过比较show slave status中的Master_Log_File, Read_Master_Log_Pos位置），
哪个slave拥有最旧的relay log
Phase 3.2: Saving Dead Master's Binlog Phase..
根据上面得到的slave的最新位置信息，将差异的二进制日志保存到MHA Manager的指定目录下。
如果在第一步骤中，判断了MHA Manager到master的ssh不可用，则会跳过这个阶段。
Phase 3.3: Determining New Master Phase..
选择新的master
Phase 3.3: New Master Diff Log Generation Phase..
将差异的relay log和master差异日志scp到新的master上。
Phase 3.4: Master Log Apply Phase..
首先，等待slave上已有的relay log都应用完。
其次，通过apply_diff_relay_logs应用差异的relay log，及差异的binlog。
应用完毕后，得到新的master binlog的文件和位置，其它slave可根据该文件和位置来建立主从复制关系。
第三，执行master_ip_failover脚本，执行如下操作
1> 将新主的read_only设置为0
2> 启动vip
Phase 4: Slaves Recovery Phase
Phase 4.1: Starting Parallel Slave Diff Log Generation Phase
为slave获取差异的relay log
因为192.168.244.30拥有最新的relay log，所以也没必要获取差异的relay log
Phase 4.2: Starting Parallel Slave Log Apply Phase
开始slave的恢复阶段
1> 将差异的relay log和master差异日志scp到slave上。
2> 应用差异日志。
3> 清除原来的复制关系，并再次执行change master命令建立新的主从同步。
如果有多个slave，则该恢复过程是并行的。
Phase 5: New master cleanup phase
从MHA的配置文件中剔除server1的配置信息
最后，生成Failover Report并发送告警邮件。
手动Failover
与自动Failover相对应的是手动Failover，即当master发生故障时，通过手动执行脚本来进行故障切换。
命令如下：
# masterha_master_switch --master_state=dead --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.244.10 --dead_master_port=3306 --new_master_host=192.168.244.30 --new_master_port=3306 --ignore_last_failover
输出日志信息如下：
--dead_master_ip=<dead_master_ip> is not set. Using 192.168.244.10.
Wed May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] MHA::MasterFailover version 0.56.
Wed May :: - [info] Starting master failover.
Wed May :: - [info]
Wed May :: - [info] * Phase : Configuration Check Phase..
Wed May :: - [info]
Wed May :: - [info] GTID failover mode =
Wed May :: - [info] Dead Servers:
Wed May :: - [info] 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Checking master reachability via MySQL(double check)...
Wed May :: - [info] ok.
Wed May :: - [info] Alive Servers:
Wed May :: - [info] 192.168.244.20(192.168.244.20:)
Wed May :: - [info] 192.168.244.30(192.168.244.30:)
Wed May :: - [info] Alive Slaves:
Wed May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Primary candidate for the new Master (candidate_master is set)
Wed May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Master 192.168.244.10(192.168.244.10:) is dead. Proceed? (yes/NO): yes
Wed May :: - [info] Starting Non-GTID based failover.
Wed May :: - [info]
Wed May :: - [info] ** Phase : Configuration Check Phase completed.
Wed May :: - [info]
Wed May :: - [info] * Phase : Dead Master Shutdown Phase..
Wed May :: - [info]
Wed May :: - [info] HealthCheck: SSH to 192.168.244.10 is reachable.
Wed May :: - [info] Forcing shutdown so that applications never connect to the current master..
Wed May :: - [info] Executing master IP deactivation script:
Wed May :: - [info] /usr/local/bin/master_ip_failover --orig_master_host=192.168.244.10 --orig_master_ip=192.168..
--orig_master_port= --command=stopssh --ssh_user=root Disabling the VIP an old master: 192.168.244.10
SIOCSIFFLAGS: Cannot assign requested address
Wed May :: - [info] done.
Wed May :: - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Wed May :: - [info] * Phase : Dead Master Shutdown Phase completed.
Wed May :: - [info]
Wed May :: - [info] * Phase : Master Recovery Phase..
Wed May :: - [info]
Wed May :: - [info] * Phase 3.1: Getting Latest Slaves Phase..
Wed May :: - [info]
Wed May :: - [info] The latest binary log file/position on all slaves is mysql-bin.:
Wed May :: - [info] Latest slaves (Slaves that received relay log files to the latest):
Wed May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Primary candidate for the new Master (candidate_master is set)
Wed May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info] The oldest binary log file/position on all slaves is mysql-bin.:
Wed May :: - [info] Oldest slaves:
Wed May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Primary candidate for the new Master (candidate_master is set)
Wed May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info]
Wed May :: - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Wed May :: - [info]
Wed May :: - [info] Fetching dead master's binary logs..
Wed May :: - [info] Executing command on the dead master 192.168.244.10(192.168.244.10:): save_binary_logs --comman
d=save --start_file=mysql-bin. --start_pos= --binlog_dir=/var/lib/mysql --output_file=/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 Creating /tmp if not exists.. ok.
Concat binary/relay logs from mysql-bin. pos to mysql-bin. EOF into /tmp/saved_master_binlog_from_192.168.244.10_330
6_20170524194420.binlog .. Binlog Checksum enabled
Dumping binlog format description event, from position to .. ok.
Dumping effective binlog data from /var/lib/mysql/mysql-bin. position to tail().. ok.
Binlog Checksum enabled
Concat succeeded.
saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog % .1KB/s :
Wed May :: - [info] scp from root@192.168.244.10:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlo
g to local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog succeeded.Wed May :: - [info] HealthCheck: SSH to 192.168.244.20 is reachable.
Wed May :: - [info] HealthCheck: SSH to 192.168.244.30 is reachable.
Wed May :: - [info]
Wed May :: - [info] * Phase 3.3: Determining New Master Phase..
Wed May :: - [info]
Wed May :: - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Wed May :: - [info] All slaves received relay logs to the same position. No need to resync each other.
Wed May :: - [info] 192.168.244.30 can be new master.
Wed May :: - [info] New master is 192.168.244.30(192.168.244.30:)
Wed May :: - [info] Starting master failover..
Wed May :: - [info]
From:
192.168.244.10(192.168.244.10:) (current master)
+--192.168.244.20(192.168.244.20:)
+--192.168.244.30(192.168.244.30:) To:
192.168.244.30(192.168.244.30:) (new master)
+--192.168.244.20(192.168.244.20:) Starting master switch from 192.168.244.10(192.168.244.10:) to 192.168.244.30(192.168.244.30:)? (yes/NO): yes
Wed May :: - [info] New master decided manually is 192.168.244.30(192.168.244.30:)
Wed May :: - [info]
Wed May :: - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Wed May :: - [info]
Wed May :: - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Wed May :: - [info] Sending binlog..
saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog % .1KB/s :
Wed May :: - [info] scp from local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog to
root@192.168.244.30:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog succeeded.Wed May :: - [info]
Wed May :: - [info] * Phase 3.4: Master Log Apply Phase..
Wed May :: - [info]
Wed May :: - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Wed May :: - [info] Starting recovery on 192.168.244.30(192.168.244.30:)..
Wed May :: - [info] Generating diffs succeeded.
Wed May :: - [info] Waiting until all relay logs are applied.
Wed May :: - [info] done.
Wed May :: - [info] Getting slave status..
Wed May :: - [info] This slave(192.168.244.30)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000002:120
). No need to recover from Exec_Master_Log_Pos.Wed May :: - [info] Connecting to the target slave host 192.168.244.30, running recover script..
Wed May :: - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='monitor' --slave_host=192.16
8.244. --slave_ip=192.168.244.30 --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog --workdir=/tmp --target_version=5.6.-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --slave_pass=xxxWed May :: - [info]
MySQL client version is 5.6.. Using --binary-mode.
Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog on 192.168.244.3
:. This may take long time...Applying log files succeeded.
Wed May :: - [info] All relay logs were successfully applied.
Wed May :: - [info] Getting new master's binlog name and position..
Wed May :: - [info] mysql-bin.:
Wed May :: - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_
HOST='192.168.244.30', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';Wed May :: - [info] Executing master IP activate script:
Wed May :: - [info] /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168..
--orig_master_ip=192.168.244.10 --orig_master_port= --new_master_host=192.168.244.30 --new_master_ip=192.168.244.30 --new_master_port= --new_master_user='monitor' --new_master_password='monitor123' Set read_only= on the new master.
Enabling the VIP 192.168.244.188 on the new master: 192.168.244.30
Wed May :: - [info] OK.
Wed May :: - [info] ** Finished master recovery successfully.
Wed May :: - [info] * Phase : Master Recovery Phase completed.
Wed May :: - [info]
Wed May :: - [info] * Phase : Slaves Recovery Phase..
Wed May :: - [info]
Wed May :: - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Wed May :: - [info]
Wed May :: - [info] -- Slave diff file generation on host 192.168.244.20(192.168.244.20:) started, pid: . Check
tmp log /masterha/app1/192.168..20_3306_20170524194420.log if it takes time..Wed May :: - [info]
Wed May :: - [info] Log messages from 192.168.244.20 ...
Wed May :: - [info]
Wed May :: - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Wed May :: - [info] End of log messages from 192.168.244.20.
Wed May :: - [info] -- 192.168.244.20(192.168.244.20:) has the latest relay log events.
Wed May :: - [info] Generating relay diff files from the latest slave succeeded.
Wed May :: - [info]
Wed May :: - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Wed May :: - [info]
Wed May :: - [info] -- Slave recovery on host 192.168.244.20(192.168.244.20:) started, pid: . Check tmp log /ma
sterha/app1/192.168..20_3306_20170524194420.log if it takes time..saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog % .1KB/s :
Wed May :: - [info]
Wed May :: - [info] Log messages from 192.168.244.20 ...
Wed May :: - [info]
Wed May :: - [info] Sending binlog..
Wed May :: - [info] scp from local:/masterha/app1/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog to
root@192.168.244.20:/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog succeeded.Wed May :: - [info] Starting recovery on 192.168.244.20(192.168.244.20:)..
Wed May :: - [info] Generating diffs succeeded.
Wed May :: - [info] Waiting until all relay logs are applied.
Wed May :: - [info] done.
Wed May :: - [info] Getting slave status..
Wed May :: - [info] This slave(192.168.244.20)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000002:120
). No need to recover from Exec_Master_Log_Pos.Wed May :: - [info] Connecting to the target slave host 192.168.244.20, running recover script..
Wed May :: - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='monitor' --slave_host=192.16
8.244. --slave_ip=192.168.244.20 --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog --workdir=/tmp --target_version=5.6.-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --slave_pass=xxxWed May :: - [info]
MySQL client version is 5.6.. Using --binary-mode.
Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.244.10_3306_20170524194420.binlog on 192.168.244.2
:. This may take long time...Applying log files succeeded.
Wed May :: - [info] All relay logs were successfully applied.
Wed May :: - [info] Resetting slave 192.168.244.20(192.168.244.20:) and starting replication from the new master
92.168.244.30(192.168.244.30:)..Wed May :: - [info] Executed CHANGE MASTER.
Wed May :: - [info] Slave started.
Wed May :: - [info] End of log messages from 192.168.244.20.
Wed May :: - [info] -- Slave recovery on host 192.168.244.20(192.168.244.20:) succeeded.
Wed May :: - [info] All new slave servers recovered successfully.
Wed May :: - [info]
Wed May :: - [info] * Phase : New master cleanup phase..
Wed May :: - [info]
Wed May :: - [info] Resetting slave info on the new master..
Wed May :: - [info] 192.168.244.30: Resetting slave info succeeded.
Wed May :: - [info] Master failover to 192.168.244.30(192.168.244.30:) completed successfully.
Wed May :: - [info] ----- Failover Report ----- app1: MySQL Master failover 192.168.244.10(192.168.244.10:) to 192.168.244.30(192.168.244.30:) succeeded Master 192.168.244.10(192.168.244.10:) is down! Check MHA Manager logs at node4 for details. Started manual(interactive) failover.
Invalidated master IP address on 192.168.244.10(192.168.244.10:)
The latest slave 192.168.244.20(192.168.244.20:) has all relay logs for recovery.
Selected 192.168.244.30(192.168.244.30:) as a new master.
192.168.244.30(192.168.244.30:): OK: Applying all logs succeeded.
192.168.244.30(192.168.244.30:): OK: Activated master IP address.
192.168.244.20(192.168.244.20:): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.244.20(192.168.244.20:): OK: Applying all logs succeeded. Slave started, replicating from 192.168.244.30(192.168.244.30:
)192.168.244.30(192.168.244.30:): Resetting slave info succeeded.
Master failover to 192.168.244.30(192.168.244.30:) completed successfully.
Wed May :: - [info] Sending mail..
Unknown option: conf
在切换的过程中，会有两次确认操作。
通过日志的输出，可以看出，手动Failover的切换逻辑和自动Failover的切换逻辑基本一致。
在上面的命令中，显示指定了--new_master_host参数，如果，没有显示指定该参数的话，则默认新主为192.168.244.20，因为在/etc/masterha/app1.cnf中将主机设置为candidate_master=1。
事实上，如果master alive的话，是不允许切换的。
Wed May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] MHA::MasterFailover version 0.56.
Wed May :: - [info] Starting master failover.
Wed May :: - [info]
Wed May :: - [info] * Phase : Configuration Check Phase..
Wed May :: - [info]
Wed May :: - [info] GTID failover mode =
Wed May :: - [info] Dead Servers:
Wed May :: - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln187] None of server is dead. Stop failover.
Wed May :: - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/local/bin/masterha_master_switch line .
在默认情况下，如果MHA检测到两次切换的时间小于8小时，则不允许进行Failover，这个时候，需指定--ignore_last_failover参数
# masterha_master_switch --master_state=dead --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.244.10 --dead_master_port=
--dead_master_ip=<dead_master_ip> is not set. Using 192.168.244.10.
Wed May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] MHA::MasterFailover version 0.56.
Wed May :: - [info] Starting master failover.
Wed May :: - [info]
Wed May :: - [info] * Phase : Configuration Check Phase..
Wed May :: - [info]
Wed May :: - [info] GTID failover mode =
Wed May :: - [info] Dead Servers:
Wed May :: - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln187] None of server is dead. Stop failover.
Wed May :: - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/local/bin/masterha_master_sw
itch line .[root@node4 ~]# masterha_master_switch --master_state=dead --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.244.10 --dead_mas
ter_port=--dead_master_ip=<dead_master_ip> is not set. Using 192.168.244.10.
Wed May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed May :: - [info] MHA::MasterFailover version 0.56.
Wed May :: - [info] Starting master failover.
Wed May :: - [info]
Wed May :: - [info] * Phase : Configuration Check Phase..
Wed May :: - [info]
Wed May :: - [info] GTID failover mode =
Wed May :: - [info] Dead Servers:
Wed May :: - [info] 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Checking master reachability via MySQL(double check)...
Wed May :: - [info] ok.
Wed May :: - [info] Alive Servers:
Wed May :: - [info] 192.168.244.20(192.168.244.20:)
Wed May :: - [info] 192.168.244.30(192.168.244.30:)
Wed May :: - [info] Alive Slaves:
Wed May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Wed May :: - [info] Primary candidate for the new Master (candidate_master is set)
Wed May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log
-bin:enabledWed May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Master 192.168.244.10(192.168.244.10:) is dead. Proceed? (yes/NO): yes
Wed May :: - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln309] Last failover was done at // ::
. Current time is too early to do failover again. If you want to do failover, manually remove /masterha/app1/app1.failover.complete and run this script again.Wed May :: - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/local/bin/masterha_master_sw
itch line .
后面附上之前提到的测试结果不理想的两种方案
方案一：
模拟步骤如下：
1. master上创建测试表
mysql> use sbtest;
Database changed mysql> create table sbtest.t1(id int primary key,col1 varchar(10),col2 varchar(10),col3 varchar(10),col4 varchar(10),col5 varchar(10),col6 varchar(10),col7 varchar(10),col8 varchar(10),col9 varchar(10),col10 varchar(10));
Query OK, 0 rows affected (0.33 sec)
2. 关闭Candicate master和Slave的主从复制。
mysql> stop slave;
Query OK, 0 rows affected (0.03 sec)
3. 在master上生成测试数据
创建存储过程
delimiter //
create procedure p1()
begin
declare v1 int default 0;
while v1 <=700000 do
insert into sbtest.t1 values(v1,'aaaaaaaaaa','bbbbbbbbbb','cccccccccc','dddddddddd','eeeeeeeeee','ffffffffff','gggggggggg','hhhhhhhhhh','iiiiiiiiii','jjjjjjjjjj');
set v1=v1+1;
if v1 %1000 =0 then
commit;
end if;
end while;
end//
delimiter ;
执行存储过程
mysql> call p1;
共执行了两次，生成了500M左右的binlog
[root@node1 ~]# ll -h /var/lib/mysql/mysql-bin.000046
-rw-rw---- 1 mysql mysql 502M Apr 24 15:18 /var/lib/mysql/mysql-bin.00004
5. 开启Candicate master和Slave的主从复制并kill掉master的mysqld进程，模拟主库发生故障，进行自动failover操作
在这里，我写了个脚本来实现开启slave复制并kill掉master mysqld进程的功能
# vim monitor_slave.py
#!/usr/bin/python
# coding=utf-8
import MySQLdb
import subprocess
import time class CheckSlaveStatus:
def __init__(self, host):
self.conn = MySQLdb.connect(host, "monitor", "monitor123")
self.cursor = self.conn.cursor()
self.cursor.execute("start slave") def get_slave_status(self):
self.cursor.execute("show slave status")
slave_status_result = self.cursor.fetchone()
slave_io_running, slave_sql_running = slave_status_result[10], slave_status_result[11]
return [slave_io_running, slave_sql_running] def quit(self):
try:
self.conn.commit()
self.conn.close()
except Exception as e:
print e def main(): check_host = ['192.168.244.30', '192.168.244.20']
check_slave_status_30 = CheckSlaveStatus(check_host[0])
check_slave_status_20 = CheckSlaveStatus(check_host[1]) for check_slave_status in [check_slave_status_30, check_slave_status_20]:
print "Begin to check slave status"
while True:
slave_status = check_slave_status.get_slave_status()
print slave_status
if slave_status == ['Yes', 'Yes']:
time.sleep(5)
break time.sleep(10)
print "Begin to kill master mysqld"
command_line="ps -ef |grep mysqld |grep -v grep |awk '{print $2}' |xargs kill -9"
p = subprocess.Popen(command_line, stdout=subprocess.PIPE, shell=True)
p.communicate() check_slave_status_30.quit()
check_slave_status_20.quit() print "Finished" if __name__ == '__main__':
main()
执行该脚本
6. 查看MHA的切换日志
Sun May :: - [warning] Got error on MySQL select ping: (MySQL server has gone away)
Sun May :: - [info] Executing secondary network check script: /usr/local/bin/masterha_secondary_check -s 192.168.244.20 -s 192.168.244.30 --user=root --master_host=192.168.244.10 --master_ip=192.168.244.10 --master_port= --user=root --master_host=192.168.244.10 --master_ip=192.168.244.10 --master_port= --master_user=monitor --masteConnection timed out during banner exchange
Sun May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sun May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sun May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Sun May :: - [warning] Got error on MySQL connect: (Lost connection to MySQL server at 'reading initial communication packet', system error: )
Sun May :: - [warning] Connection failed time(s)..
Monitoring server 192.168.244.20 is reachable, Master is not reachable from 192.168.244.20. OK.
Sun May :: - [warning] HealthCheck: SSH to 192.168.244.10 is NOT reachable.
Monitoring server 192.168.244.30 is reachable, Master is not reachable from 192.168.244.30. OK.
Sun May :: - [info] Master is not reachable from all other monitoring servers. Failover should start.
Sun May :: - [warning] Master is not reachable from health checker!
Sun May :: - [warning] Master 192.168.244.10(192.168.244.10:) is not reachable!
Sun May :: - [warning] SSH is NOT reachable.
Sun May :: - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..
Sun May :: - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sun May :: - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sun May :: - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sun May :: - [info] GTID failover mode =
Sun May :: - [info] Dead Servers:
Sun May :: - [info] 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Alive Servers:
Sun May :: - [info] 192.168.244.20(192.168.244.20:)
Sun May :: - [info] 192.168.244.30(192.168.244.30:)
Sun May :: - [info] Alive Slaves:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Checking slave configurations..
Sun May :: - [info] Checking replication filtering settings..
Sun May :: - [info] Replication filtering check ok.
Sun May :: - [info] Master is down!
Sun May :: - [info] Terminating monitoring script.
Sun May :: - [info] Got exit code (Master dead).
Sun May :: - [info] MHA::MasterFailover version 0.56.
Sun May :: - [info] Starting master failover.
Sun May :: - [info]
Sun May :: - [info] * Phase : Configuration Check Phase..
Sun May :: - [info]
Sun May :: - [info] GTID failover mode =
Sun May :: - [info] Dead Servers:
Sun May :: - [info] 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Checking master reachability via MySQL(double check)...
Sun May :: - [info] ok.
Sun May :: - [info] Alive Servers:
Sun May :: - [info] 192.168.244.20(192.168.244.20:)
Sun May :: - [info] 192.168.244.30(192.168.244.30:)
Sun May :: - [info] Alive Slaves:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Starting Non-GTID based failover.
Sun May :: - [info]
Sun May :: - [info] ** Phase : Configuration Check Phase completed.
Sun May :: - [info]
Sun May :: - [info] * Phase : Dead Master Shutdown Phase..
Sun May :: - [info]
Sun May :: - [info] Forcing shutdown so that applications never connect to the current master..
Sun May :: - [info] Executing master IP deactivation script:
Sun May :: - [info] /usr/local/bin/master_ip_failover --orig_master_host=192.168.244.10 --orig_master_ip=192.168.244.10 --orig_master_port= --command=stop
Disabling the VIP an old master: 192.168.244.10
Sun May :: - [info] done.
Sun May :: - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Sun May :: - [info] * Phase : Dead Master Shutdown Phase completed.
Sun May :: - [info]
Sun May :: - [info] * Phase : Master Recovery Phase..
Sun May :: - [info]
Sun May :: - [info] * Phase 3.1: Getting Latest Slaves Phase..
Sun May :: - [info]
Sun May :: - [info] The latest binary log file/position on all slaves is mysql-bin.:
Sun May :: - [info] Latest slaves (Slaves that received relay log files to the latest):
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] The oldest binary log file/position on all slaves is mysql-bin.:
Sun May :: - [info] Oldest slaves:
Sun May :: - [info] 192.168.244.30(192.168.244.30:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info]
Sun May :: - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Sun May :: - [info]
Sun May :: - [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.
Sun May :: - [info]
Sun May :: - [info] * Phase 3.3: Determining New Master Phase..
Sun May :: - [info]
Sun May :: - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Sun May :: - [info] HealthCheck: SSH to 192.168.244.20 is reachable.
Sun May :: - [info] Checking whether 192.168.244.20 has relay logs from the oldest position..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=find --latest_mlf=mysql-bin. --latest_rmlp= --target_mlf=mysql-bin. --target_rmlp= --server_id= --workdir=/tmp --timestamp= --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/ :
Opening /var/lib/mysql/relay-log.info ... ok.
Relay log found at /var/lib/mysql, up to mysqld-relay-bin.
Fast relay log position search succeeded.
Target relay log file/position found. start_file:mysqld-relay-bin., start_pos:.
Target relay log FOUND!
Sun May :: - [info] OK. 192.168.244.20 has all relay logs.
Sun May :: - [info] HealthCheck: SSH to 192.168.244.30 is reachable.
Sun May :: - [info] Searching new master from slaves..
Sun May :: - [info] Candidate masters from the configuration file:
Sun May :: - [info] 192.168.244.20(192.168.244.20:) Version=5.6.-log (oldest major version between slaves) log-bin:enabled
Sun May :: - [info] Replicating from 192.168.244.10(192.168.244.10:)
Sun May :: - [info] Primary candidate for the new Master (candidate_master is set)
Sun May :: - [info] Non-candidate masters:
Sun May :: - [info] Searching from candidate_master slaves which have received the latest relay log events..
Sun May :: - [info] New master is 192.168.244.20(192.168.244.20:)
Sun May :: - [info] Starting master failover..
Sun May :: - [info]
From:
192.168.244.10(192.168.244.10:) (current master)
+--192.168.244.20(192.168.244.20:)
+--192.168.244.30(192.168.244.30:) To:
192.168.244.20(192.168.244.20:) (new master)
+--192.168.244.30(192.168.244.30:)
Sun May :: - [info]
Sun May :: - [info] * Phase 3.3: New Master Diff Log Generation Phase..
Sun May :: - [info]
Sun May :: - [info] This server has all relay logs. No need to generate diff files from the latest slave.
Sun May :: - [info]
Sun May :: - [info] * Phase 3.4: Master Log Apply Phase..
Sun May :: - [info]
Sun May :: - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Sun May :: - [info] Starting recovery on 192.168.244.20(192.168.244.20:)..
Sun May :: - [info] This server has all relay logs. Waiting all logs to be applied..
Sun May :: - [info] done.
Sun May :: - [info] All relay logs were successfully applied.
Sun May :: - [info] Getting new master's binlog name and position..
Sun May :: - [info] mysql-bin.:
Sun May :: - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.244.20', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000010', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Sun May :: - [info] Executing master IP activate script:
Sun May :: - [info] /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.244.10 --orig_master_ip=192.168.244.10 --orig_master_port= --new_master_host=192.168.244.20 --new_master_ip=192.168.244.20 --new_master_port= --new_master_user='monitor' --new_master_password='monitor123'
Set read_only= on the new master.
Enabling the VIP 192.168.244.188 on the new master: 192.168.244.20
Sun May :: - [info] OK.
Sun May :: - [info] ** Finished master recovery successfully.
Sun May :: - [info] * Phase : Master Recovery Phase completed.
Sun May :: - [info]
Sun May :: - [info] * Phase : Slaves Recovery Phase..
Sun May :: - [info]
Sun May :: - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Sun May :: - [info]
Sun May :: - [info] -- Slave diff file generation on host 192.168.244.30(192.168.244.30:) started, pid: . Check tmp log /masterha/app1/192.168..30_3306_20170521094708.log if it takes time..
Sun May :: - [info]
Sun May :: - [info] Log messages from 192.168.244.30 ...
Sun May :: - [info]
Sun May :: - [info] Server 192.168.244.30 received relay logs up to: mysql-bin.:
Sun May :: - [info] Need to get diffs from the latest slave(192.168.244.20) up to: mysql-bin.: (using the latest slave's relay logs)
Sun May :: - [info] Connecting to the latest slave host 192.168.244.20, generating diff relay log files..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=generate_and_send --scp_user=root --scp_host=192.168.244.30 --latest_mlf=mysql-bin. --latest_rmlp= --target_mlf=mysql-bin. --target_rmlp= --server_id= --diff_file_readtolatest=/tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog --workdir=/tmp --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --relay_dir=/var/lib/mysql/
Sun May :: - [info]
Opening /var/lib/mysql/relay-log.info ... ok.
Relay log found at /var/lib/mysql, up to mysqld-relay-bin.
Fast relay log position search succeeded.
Target relay log file/position found. start_file:mysqld-relay-bin., start_pos:.
Concat binary/relay logs from mysqld-relay-bin. pos to mysqld-relay-bin. EOF into /tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog ..
Binlog Checksum enabled
Binlog Checksum enabled
Dumping binlog format description event, from position to .. ok.
Dumping effective binlog data from /var/lib/mysql/mysqld-relay-bin. position to tail().. ok.
Binlog Checksum enabled
Binlog Checksum enabled
Concat succeeded.
Generating diff relay log succeeded. Saved at /tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog .
scp node2:/tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog to root@192.168.244.30() succeeded.
Sun May :: - [info] Generating diff files succeeded.
Sun May :: - [info] End of log messages from 192.168.244.30.
Sun May :: - [info] -- Slave diff log generation on host 192.168.244.30(192.168.244.30:) succeeded.
Sun May :: - [info] Generating relay diff files from the latest slave succeeded.
Sun May :: - [info]
Sun May :: - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Sun May :: - [info]
Sun May :: - [info] -- Slave recovery on host 192.168.244.30(192.168.244.30:) started, pid: . Check tmp log /masterha/app1/192.168..30_3306_20170521094708.log if it takes time..
Sun May :: - [info]
Sun May :: - [info] Log messages from 192.168.244.30 ...
Sun May :: - [info]
Sun May :: - [info] Starting recovery on 192.168.244.30(192.168.244.30:)..
Sun May :: - [info] Generating diffs succeeded.
Sun May :: - [info] Waiting until all relay logs are applied.
Sun May :: - [info] done.
Sun May :: - [info] Getting slave status..
Sun May :: - [info] This slave(192.168.244.30)'s Exec_Master_Log_Pos(mysql-bin.000001:35083010) does not equal to Read_Master_Log_Pos(mysql-bin.000001:35083093). It is likely that relay log was cut during transaction. Need to recover from Exec_Master_Log_Pos.
Sun May :: - [info] Saving local relay logs from exec pos to read pos on 192.168.244.30: from mysqld-relay-bin.: to the end of the relay log..
Sun May :: - [info] Executing command : save_binary_logs --command=save --start_file=mysqld-relay-bin. --start_pos= --output_file=/tmp/relay_from_exec_to_read_192.168.244.30_3306_20170521094708.binlog --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info --binlog_dir=/var/lib/mysql/
Sun May :: - [info]
Creating /tmp if not exists.. ok.
Concat binary/relay logs from mysqld-relay-bin. pos to mysqld-relay-bin. EOF into /tmp/relay_from_exec_to_read_192.168.244.30_3306_20170521094708.binlog ..
Binlog Checksum enabled
Binlog Checksum enabled
Dumping binlog format description event, from position to .. ok.
Dumping effective binlog data from /var/lib/mysql/mysqld-relay-bin. position to tail().. ok.
Binlog Checksum enabled
Binlog Checksum enabled
Concat succeeded.
Sun May :: - [info] Connecting to the target slave host 192.168.244.30, running recover script..
Sun May :: - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user='monitor' --slave_host=192.168.244.30 --slave_ip=192.168.244.30 --slave_port= --apply_files=/tmp/relay_from_exec_to_read_192.168.244.30_3306_20170521094708.binlog,/tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog --workdir=/tmp --target_version=5.6.-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.56 --slave_pass=xxx
Sun May :: - [info]
Concat all apply files to /tmp/total_binlog_for_192.168.244.30_3306..binlog ..
Copying the first binlog file /tmp/relay_from_exec_to_read_192.168.244.30_3306_20170521094708.binlog to /tmp/total_binlog_for_192.168.244.30_3306..binlog.. ok.
Dumping binlog head events (rotate events), skipping format description events from /tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog.. Binlog Checksum enabled
Binlog Checksum enabled
dumped up to pos . ok.
/tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog has effective binlog events from pos .
Dumping effective binlog data from /tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog position to tail().. ok.
Concat succeeded.
All apply target binary logs are concatinated at /tmp/total_binlog_for_192.168.244.30_3306..binlog .
MySQL client version is 5.6.. Using --binary-mode.
Applying differential binary/relay log files /tmp/relay_from_exec_to_read_192.168.244.30_3306_20170521094708.binlog,/tmp/relay_from_read_to_latest_192.168.244.30_3306_20170521094708.binlog on 192.168.244.30:. This may take long time...
Applying log files succeeded.
Sun May :: - [info] All relay logs were successfully applied.
Sun May :: - [info] Resetting slave 192.168.244.30(192.168.244.30:) and starting replication from the new master 192.168.244.20(192.168.244.20:)..
Sun May :: - [info] Executed CHANGE MASTER.
Sun May :: - [info] Slave started.
Sun May :: - [info] End of log messages from 192.168.244.30.
Sun May :: - [info] -- Slave recovery on host 192.168.244.30(192.168.244.30:) succeeded.
Sun May :: - [info] All new slave servers recovered successfully.
Sun May :: - [info]
Sun May :: - [info] * Phase : New master cleanup phase..
Sun May :: - [info]
Sun May :: - [info] Resetting slave info on the new master..
Sun May :: - [info] 192.168.244.20: Resetting slave info succeeded.
Sun May :: - [info] Master failover to 192.168.244.20(192.168.244.20:) completed successfully.
Sun May :: - [info] Deleted server1 entry from /etc/masterha/app1.cnf .
Sun May :: - [info] ----- Failover Report ----- app1: MySQL Master failover 192.168.244.10(192.168.244.10:) to 192.168.244.20(192.168.244.20:) succeeded Master 192.168.244.10(192.168.244.10:) is down! Check MHA Manager logs at node4:/masterha/app1/manager.log for details. Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.244.10(192.168.244.10:)
The latest slave 192.168.244.20(192.168.244.20:) has all relay logs for recovery.
Selected 192.168.244.20(192.168.244.20:) as a new master.
192.168.244.20(192.168.244.20:): OK: Applying all logs succeeded.
192.168.244.20(192.168.244.20:): OK: Activated master IP address.
192.168.244.30(192.168.244.30:): Generating differential relay logs up to 192.168.244.20(192.168.244.20:)succeeded.
Generating relay diff files from the latest slave succeeded.
192.168.244.30(192.168.244.30:): OK: Applying all logs succeeded. Slave started, replicating from 192.168.244.20(192.168.244.20:)
192.168.244.20(192.168.244.20:): Resetting slave info succeeded.
Master failover to 192.168.244.20(192.168.244.20:) completed successfully.
Sun May :: - [info] Sending mail..
Unknown option: conf
方案二
对Candicate master上和Slave上的网卡进行带宽限制
Candicate master
[root@node2 ~]# /sbin/tc qdisc add dev eth0 root tbf rate 50kbit latency 50ms burst 15kb
Slave
/sbin/tc qdisc add dev eth0 root tbf rate 80kbit latency 50ms burst 15kb
注意：Candicate master的网卡限制在50kbit，slave的网卡限制在80kbit，
要确保Candicate master的小于slave的，这样才能模拟出Candicate master上relay log的位置小于slave上relay log的位置。
关于如何确认网卡的速率控制到多大合适，
可通过压测，测试master的吞吐量，
以及结合如下方法，测试主机之间的传输速率来确定网卡合适的速率。
[root@node1 ~]# dd if=/dev/zero of=hello.txt bs=100M count=1
[root@node1 ~]# time scp hello.txt 192.168.244.20:/tmp/
hello.txt 100% 100MB 2.6MB/s 00:39
参考
《深入浅出MySQL》
MySQL高可用方案MHA自动Failover与手动Failover的实践及原理的更多相关文章
- MySQL高可用方案--MHA部署及故障转移
架构设计及必要配置 主机环境 IP 主机名 担任角色 192.168.192.128 node_master MySQL-Master| ...
- mysql高可用方案MHA介绍
mysql高可用方案MHA介绍 概述 MHA是一位日本MySQL大牛用Perl写的一套MySQL故障切换方案,来保证数据库系统的高可用.在宕机的时间内(通常10-30秒内),完成故障切换,部署MHA, ...
- MySQL高可用方案MHA在线切换的步骤及原理
在日常工作中,会碰到如下的场景,如mysql数据库升级,主服务器硬件升级等,这个时候就需要将写操作切换到另外一台服务器上,那么如何进行在线切换呢?同时,要求切换过程短,对业务的影响比较小. MHA就提 ...
- MySQL高可用方案MHA的部署和原理
MHA(Master High Availability)是一套相对成熟的MySQL高可用方案,能做到在0~30s内自动完成数据库的故障切换操作,在master服务器不宕机的情况下,基本能保证数据的一 ...
- mysql 高可用方案MHA介绍
概述 MHA是一位日本MySQL大牛用Perl写的一套MySQL故障切换方案,来保证数据库系统的高可用.在宕机的时间内(通常10—30秒内),完成故障切换,部署MHA,可避免主从一致性问题,节约购买新 ...
- MySQL高可用方案--MHA原理
简介 MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司youshimaton(现就职于Facebook公司)开发,是日 ...
- MySQL高可用方案 MHA之二 master_ip_failover
异步主从复制架构master:10.150.20.90 ed3jrdba90slave:10.15.20.97 ed3jrdba9710.150.20.132 ed3jrdba132manager:1 ...
- MySQL高可用方案 MHA之一MHA安装
MHA0.58安装 MHA(Master High Availability)由两部分组成:MHA Manager(管理节点)和MHA Node(数据节点).管理节点mha4mysql-manager ...
- （转）MySQL高可用方案MHA的部署和原理
背后深层次的逻辑: MHA Node则运行在每个mysql节点上,MHA Manager会定时探测集群中的master节点,当master出现故障时,它自动将最新数据的slave提升为master,然 ...
随机推荐
- C#中的DateTime是值类型还是引用类型
近期遇到了DateTime到底是值类型还是引用类型的疑惑,顺势较深入地了解一下DateTime相关的内容 结论:DateTime是值类型,因为DateTime是结构体,而结构体继承自Syste.Val ...
- 基于Flink的windows--简介
新的一年,新的开始,新的习惯,现在开始. 1.简介 Flink是德国一家公司名为dataArtisans的产品,2016年正式被apache提升为顶级项目(地位同spark.storm等开源架构).并 ...
- 基本数据结构——堆(Heap)的基本概念及其操作
基本数据结构――堆的基本概念及其操作 小广告:福建安溪一中在线评测系统 Online Judge 在我刚听到堆这个名词的时候,我认为它是一堆东西的集合．．． 但其实吧它是利用完全二叉树的结构来维护一组 ...
- Unity 相机的聚焦功能
摘要:本文原创,转载请注明出处 需求: 在游戏的任务编辑场景进行编辑的时候,摄像机需要在多个需要编辑的物体之间来回切换,如果只是用摄像机的移动旋转,对于相对位置较近的物体还好说,当相对位置过远的时候, ...
- linux网络编程（socket）之面向连接（TCP/IP）
1.流程 服务器: 创建socket: 绑定端口: 监听: 监听到有连接请求,接受请求: 建立连接,开始对话. 客户端: 创建socket: 请求建立连接: 连接建立成功,开始对话. 2.实例代码 / ...
- 一、AspNet Core通过控制台编译程序的基本指令：
1.先创建文件夹 mkdir "文件夹"2.在对应的文件夹里边 用 dotnet new 命令创建了Program.cs和project.json俩个文件3.使用 dotnet r ...
- C#网络程序设计(3)网络传输编程之TCP编程
网络传输编程指基于各种网络协议进行编程,包括TCP编程,UDP编程,P2P编程.本节介绍TCP编程. (1)TCP简介: TCP是TCP/IP体系中最重要的传输层协议,它提供全双工和可 ...
- angularjs中常用的ng指令介绍【转载】
原文:http://www.cnblogs.com/lvdabao/p/3379659.html 一.模板中可使用的东西及表达式 模板中可以使用的东西包括以下四种: 指令(directive).ng提 ...
- BackgroundWorker的DoWork方法中发生异常无法传递到RunWorkedCompleted方法
在使用C#的BackgroundWorker时需要在UI界面上显示DoWork中发生的异常,但怎么调试都无法跳转到界面上,异常也不会传递到RunWorkerCompleted方法中(e.Error为空 ...
- bzoj4825 [Hnoi2017]单旋
Description H 国是一个热爱写代码的国家,那里的人们很小去学校学习写各种各样的数据结构.伸展树(splay)是一种数据结构,因为代码好写,功能多,效率高,掌握这种数据结构成为了 H 国的必 ...