MySQL5.7一主两从MHA自动切换

这篇文章主要讲解了"MySQL5.7一主两从MHA自动切换"，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习"MySQL5.7一主两从MHA自动切换"吧！

数据库架构：一主两从

master：192.168.8.57

slave1：192.168.8.58

slave2：192.168.8.59

manager：192.168.8.60

MHA工具包：

mha4mysql-manager-0.58.tar.gz

mha4mysql-node-0.58.tar.gz

一、master添加vip

/sbin/ifconfig enp0s3:1 192.168.8.88/24

ifconfigenp0s3: flags=4163  mtu 1500        inet 192.168.8.57  netmask 255.255.255.0  broadcast 192.168.8.255        inet6 fe80::5198:593b:cdc5:1f90  prefixlen 64  scopeid 0x20        ether 08:00:27:c0:45:0d  txqueuelen 1000  (Ethernet)        RX packets 72386  bytes 9442794 (9.0 MiB)        RX errors 0  dropped 0  overruns 0  frame 0        TX packets 24221  bytes 2963104 (2.8 MiB)        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0enp0s3:1: flags=4163  mtu 1500        inet 192.168.8.88  netmask 255.255.255.0  broadcast 192.168.8.255        ether 08:00:27:c0:45:0d  txqueuelen 1000  (Ethernet)lo: flags=73  mtu 65536        inet 127.0.0.1  netmask 255.0.0.0        inet6 ::1  prefixlen 128  scopeid 0x10        loop  txqueuelen 1000  (Local Loopback)        RX packets 84  bytes 9492 (9.2 KiB)        RX errors 0  dropped 0  overruns 0  frame 0        TX packets 84  bytes 9492 (9.2 KiB)        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0virbr0: flags=4099  mtu 1500        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255        ether 52:54:00:f4:55:bb  txqueuelen 1000  (Ethernet)        RX packets 0  bytes 0 (0.0 B)        RX errors 0  dropped 0  overruns 0  frame 0        TX packets 0  bytes 0 (0.0 B)        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

二、failover 自动切换测试

1.手动停止master的MySQL进程

mysqladmin -uroot -pmysql shutdown

2.查看manager日志

[root@manager bin]# tail -f /var/log/masterha/app1/manager.logThu Oct 25 19:34:53 2018 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)Thu Oct 25 19:34:53 2018 - [info] Executing SSH check script: exit 0Thu Oct 25 19:34:53 2018 - [info] Executing secondary network check script: /usr/local/bin/masterha_secondary_check -s 192.168.8.58 -s 192.168.8.59  --user=root  --master_host=192.168.8.57  --master_ip=192.168.8.57  --master_port=3306 --master_user=root --master_password=mysql --ping_type=SELECTThu Oct 25 19:34:53 2018 - [info] HealthCheck: SSH to 192.168.8.57 is reachable.Monitoring server 192.168.8.58 is reachable, Master is not reachable from 192.168.8.58. OK.Thu Oct 25 19:34:54 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.8.57' (111))Thu Oct 25 19:34:54 2018 - [warning] Connection failed 2 time(s)..Monitoring server 192.168.8.59 is reachable, Master is not reachable from 192.168.8.59. OK.Thu Oct 25 19:34:54 2018 - [info] Master is not reachable from all other monitoring servers. Failover should start.Thu Oct 25 19:34:55 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.8.57' (111))Thu Oct 25 19:34:55 2018 - [warning] Connection failed 3 time(s)..Thu Oct 25 19:34:56 2018 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.8.57' (111))Thu Oct 25 19:34:56 2018 - [warning] Connection failed 4 time(s)..Thu Oct 25 19:34:56 2018 - [warning] Master is not reachable from health checker!Thu Oct 25 19:34:56 2018 - [warning] Master 192.168.8.57(192.168.8.57:3306) is not reachable!Thu Oct 25 19:34:56 2018 - [warning] SSH is reachable.Thu Oct 25 19:34:56 2018 - [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..Thu Oct 25 19:34:56 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Thu Oct 25 19:34:56 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..Thu Oct 25 19:34:56 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..Thu Oct 25 19:34:57 2018 - [info] GTID failover mode = 1Thu Oct 25 19:34:57 2018 - [info] Dead Servers:Thu Oct 25 19:34:57 2018 - [info]   192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:57 2018 - [info] Alive Servers:Thu Oct 25 19:34:57 2018 - [info]   192.168.8.58(192.168.8.58:3306)Thu Oct 25 19:34:57 2018 - [info]   192.168.8.59(192.168.8.59:3306)Thu Oct 25 19:34:57 2018 - [info] Alive Slaves:Thu Oct 25 19:34:57 2018 - [info]   192.168.8.58(192.168.8.58:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:57 2018 - [info]     GTID ONThu Oct 25 19:34:57 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:57 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 19:34:57 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:57 2018 - [info]     GTID ONThu Oct 25 19:34:57 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:57 2018 - [info] Checking slave configurations..Thu Oct 25 19:34:57 2018 - [info] Checking replication filtering settings..Thu Oct 25 19:34:57 2018 - [info]  Replication filtering check ok.Thu Oct 25 19:34:57 2018 - [info] Master is down!Thu Oct 25 19:34:57 2018 - [info] Terminating monitoring script.Thu Oct 25 19:34:57 2018 - [info] Got exit code 20 (Master dead).Thu Oct 25 19:34:57 2018 - [info] MHA::MasterFailover version 0.58.Thu Oct 25 19:34:57 2018 - [info] Starting master failover.Thu Oct 25 19:34:57 2018 - [info] Thu Oct 25 19:34:57 2018 - [info] * Phase 1: Configuration Check Phase..Thu Oct 25 19:34:57 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] GTID failover mode = 1Thu Oct 25 19:34:58 2018 - [info] Dead Servers:Thu Oct 25 19:34:58 2018 - [info]   192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info] Checking master reachability via MySQL(double check)...Thu Oct 25 19:34:58 2018 - [info]  ok.Thu Oct 25 19:34:58 2018 - [info] Alive Servers:Thu Oct 25 19:34:58 2018 - [info]   192.168.8.58(192.168.8.58:3306)Thu Oct 25 19:34:58 2018 - [info]   192.168.8.59(192.168.8.59:3306)Thu Oct 25 19:34:58 2018 - [info] Alive Slaves:Thu Oct 25 19:34:58 2018 - [info]   192.168.8.58(192.168.8.58:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 19:34:58 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info] Starting GTID based failover.Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] ** Phase 1: Configuration Check Phase completed.Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 2: Dead Master Shutdown Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] Forcing shutdown so that applications never connect to the current master..Thu Oct 25 19:34:58 2018 - [info] Executing master IP deactivation script:Thu Oct 25 19:34:58 2018 - [info]   /usr/local/bin/master_ip_failover --orig_master_host=192.168.8.57 --orig_master_ip=192.168.8.57 --orig_master_port=3306 --command=stopssh --ssh_user=root  Thu Oct 25 19:34:58 2018 - [info]  done.Thu Oct 25 19:34:58 2018 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.Thu Oct 25 19:34:58 2018 - [info] * Phase 2: Dead Master Shutdown Phase completed.Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 3: Master Recovery Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 3.1: Getting Latest Slaves Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] The latest binary log file/position on all slaves is mysql-bin.000010:707Thu Oct 25 19:34:58 2018 - [info] Retrieved Gtid Set: a92f70a4-d5ea-11e8-af28-080027c0450d:7-9Thu Oct 25 19:34:58 2018 - [info] Latest slaves (Slaves that received relay log files to the latest):Thu Oct 25 19:34:58 2018 - [info]   192.168.8.58(192.168.8.58:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 19:34:58 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info] The oldest binary log file/position on all slaves is mysql-bin.000010:707Thu Oct 25 19:34:58 2018 - [info] Retrieved Gtid Set: a92f70a4-d5ea-11e8-af28-080027c0450d:7-9Thu Oct 25 19:34:58 2018 - [info] Oldest slaves:Thu Oct 25 19:34:58 2018 - [info]   192.168.8.58(192.168.8.58:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 19:34:58 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 3.3: Determining New Master Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] Searching new master from slaves..Thu Oct 25 19:34:58 2018 - [info]  Candidate masters from the configuration file:Thu Oct 25 19:34:58 2018 - [info]   192.168.8.58(192.168.8.58:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 19:34:58 2018 - [info]     GTID ONThu Oct 25 19:34:58 2018 - [info]     Replicating from 192.168.8.57(192.168.8.57:3306)Thu Oct 25 19:34:58 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 19:34:58 2018 - [info]  Non-candidate masters:Thu Oct 25 19:34:58 2018 - [info]  Searching from candidate_master slaves which have received the latest relay log events..Thu Oct 25 19:34:58 2018 - [info] New master is 192.168.8.58(192.168.8.58:3306)Thu Oct 25 19:34:58 2018 - [info] Starting master failover..Thu Oct 25 19:34:58 2018 - [info] From:192.168.8.57(192.168.8.57:3306) (current master) +--192.168.8.58(192.168.8.58:3306) +--192.168.8.59(192.168.8.59:3306)To:192.168.8.58(192.168.8.58:3306) (new master) +--192.168.8.59(192.168.8.59:3306)Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 3.3: New Master Recovery Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info]  Waiting all logs to be applied.. Thu Oct 25 19:34:58 2018 - [info]   done.Thu Oct 25 19:34:58 2018 - [info] Getting new master's binlog name and position..Thu Oct 25 19:34:58 2018 - [info]  mysql-bin.000010:747Thu Oct 25 19:34:58 2018 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.8.58', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxx';Thu Oct 25 19:34:58 2018 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: mysql-bin.000010, 747, a92f70a4-d5ea-11e8-af28-080027c0450d:1-9,a92f70a4-d5ea-11e8-af28-080027c0450f:1-4Thu Oct 25 19:34:58 2018 - [info] Executing master IP activate script:Thu Oct 25 19:34:58 2018 - [info]   /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.8.57 --orig_master_ip=192.168.8.57 --orig_master_port=3306 --new_master_host=192.168.8.58 --new_master_ip=192.168.8.58 --new_master_port=3306 --new_master_user='root'   --new_master_password=xxxUndefined subroutine &main::FIXME_xxx_create_user called at /usr/local/bin/master_ip_failover line 94.Set read_only=0 on the new master.Creating app user on the new master..Thu Oct 25 19:34:58 2018 - [error][/usr/lib/perl5/vendor_perl/MHA/MasterFailover.pm, ln1612]  Failed to activate master IP address for 192.168.8.58(192.168.8.58:3306) with return code 10:0Thu Oct 25 19:34:58 2018 - [warning] Proceeding.Thu Oct 25 19:34:58 2018 - [info] ** Finished master recovery successfully.Thu Oct 25 19:34:58 2018 - [info] * Phase 3: Master Recovery Phase completed.Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 4: Slaves Recovery Phase..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] * Phase 4.1: Starting Slaves in parallel..Thu Oct 25 19:34:58 2018 - [info] Thu Oct 25 19:34:58 2018 - [info] -- Slave recovery on host 192.168.8.59(192.168.8.59:3306) started, pid: 20757. Check tmp log /var/log/masterha/app1/192.168.8.59_3306_20181025193457.log if it takes time..Thu Oct 25 19:34:59 2018 - [info] Thu Oct 25 19:34:59 2018 - [info] Log messages from 192.168.8.59 ...Thu Oct 25 19:34:59 2018 - [info] Thu Oct 25 19:34:58 2018 - [info]  Resetting slave 192.168.8.59(192.168.8.59:3306) and starting replication from the new master 192.168.8.58(192.168.8.58:3306)..Thu Oct 25 19:34:58 2018 - [info]  Executed CHANGE MASTER.Thu Oct 25 19:34:58 2018 - [info]  Slave started.Thu Oct 25 19:34:58 2018 - [info]  gtid_wait(a92f70a4-d5ea-11e8-af28-080027c0450d:1-9,a92f70a4-d5ea-11e8-af28-080027c0450f:1-4) completed on 192.168.8.59(192.168.8.59:3306). Executed 0 events.Thu Oct 25 19:34:59 2018 - [info] End of log messages from 192.168.8.59.Thu Oct 25 19:34:59 2018 - [info] -- Slave on host 192.168.8.59(192.168.8.59:3306) started.Thu Oct 25 19:34:59 2018 - [info] All new slave servers recovered successfully.Thu Oct 25 19:34:59 2018 - [info] Thu Oct 25 19:34:59 2018 - [info] * Phase 5: New master cleanup phase..Thu Oct 25 19:34:59 2018 - [info] Thu Oct 25 19:34:59 2018 - [info] Resetting slave info on the new master..Thu Oct 25 19:35:00 2018 - [info]  192.168.8.58: Resetting slave info succeeded.Thu Oct 25 19:35:00 2018 - [info] Master failover to 192.168.8.58(192.168.8.58:3306) completed successfully.Thu Oct 25 19:35:00 2018 - [info] Deleted server1 entry from /etc/masterha/app1.cnf .Thu Oct 25 19:35:00 2018 - [info] ----- Failover Report -----app1: MySQL Master failover 192.168.8.57(192.168.8.57:3306) to 192.168.8.58(192.168.8.58:3306) succeededMaster 192.168.8.57(192.168.8.57:3306) is down!Check MHA Manager logs at manager:/var/log/masterha/app1/manager.log for details.Started automated(non-interactive) failover.Invalidated master IP address on 192.168.8.57(192.168.8.57:3306)Selected 192.168.8.58(192.168.8.58:3306) as a new master.192.168.8.58(192.168.8.58:3306): OK: Applying all logs succeeded.Failed to activate master IP address for 192.168.8.58(192.168.8.58:3306) with return code 10:0192.168.8.59(192.168.8.59:3306): OK: Slave started, replicating from 192.168.8.58(192.168.8.58:3306)192.168.8.58(192.168.8.58:3306): Resetting slave info succeeded.Master failover to 192.168.8.58(192.168.8.58:3306) completed successfully.Thu Oct 25 19:35:00 2018 - [info] Sending mail..

日志中显示主库已经切换，新的主库为192.168.8.58

3.查看主机192.168.8.58和192.168.8.59的信息

192.168.8.58

mysql> show slave status \GEmpty set (0.00 sec)mysql> show master status \G*************************** 1. row ***************************             File: mysql-bin.000010         Position: 747     Binlog_Do_DB:  Binlog_Ignore_DB: Executed_Gtid_Set: a92f70a4-d5ea-11e8-af28-080027c0450d:1-9,a92f70a4-d5ea-11e8-af28-080027c0450f:1-41 row in set (0.00 sec)

mysql> show variables like 'read_only';+---------------+-------+| Variable_name | Value |+---------------+-------+| read_only     | OFF   |+---------------+-------+

192.168.8.59

mysql> show slave status \G*************************** 1. row ***************************               Slave_IO_State: Waiting for master to send event                  Master_Host: 192.168.8.58                  Master_User: repl                  Master_Port: 3306                Connect_Retry: 60              Master_Log_File: mysql-bin.000010          Read_Master_Log_Pos: 747               Relay_Log_File: slave2-relay-bin.000002                Relay_Log_Pos: 414        Relay_Master_Log_File: mysql-bin.000010             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: 747              Relay_Log_Space: 622              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: 0Master_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: 58                  Master_UUID: a92f70a4-d5ea-11e8-af28-080027c0450f             Master_Info_File: /mysql/data/master.info                    SQL_Delay: 0          SQL_Remaining_Delay: NULL      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates           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: a92f70a4-d5ea-11e8-af28-080027c0450b:1-4,a92f70a4-d5ea-11e8-af28-080027c0450d:1-9,a92f70a4-d5ea-11e8-af28-080027c0450f:1-4                Auto_Position: 1         Replicate_Rewrite_DB:                  Channel_Name:            Master_TLS_Version:

mysql> show variables like 'read_only';+---------------+-------+| Variable_name | Value |+---------------+-------+| read_only     | ON    |+---------------+-------+

可以看到192.168.8.58变成了新的主库，read_only变成了OFF，192.168.8.59作为192.168.8.58的从库，read_only依然为ON。

4.主从数据测试

在192.168.8.58创建表t7

mysql> create table t7(id int(6));Query OK, 0 rows affected (0.04 sec)mysql> show tables;+----------------+| Tables_in_test |+----------------+| t1             || t2             || t3             || t4             || t5             || t6             || t7             |+----------------+

在192.168.8.59进行查看

mysql> show tables;+----------------+| Tables_in_test |+----------------+| t1             || t2             || t3             || t4             || t5             || t6             || t7             |+----------------+

可以看到新的主从复制正常。

5.切换完之后你会发现 MHA Manager 监控程序会自动死掉，官网有如下解释和解决方式：

Running MHA Manager from daemontools

Currently MHA Manager process does not run as a daemon. if failover completed

successfully or the master process was killed by accident, the manager stops

working. to run as a daemon, daemontool. or any external daemon program

can be used. Here is an example to run from daemontools.

解决方法：

vi /usr/local/bin/manager_status_check#!/bin/bashwhile :doMGECHECK=`ps -ef|grep masterha_manager |egrep -v grep| wc -l`if [ $MGECHECK -eq 0 ];then/usr/local/bin/masterha_start.shelseecho "MHA manager start"fisleep 5done

chmod u+x /usr/local/bin/manager_status_checknohup /usr/local/bin/manager_status_check &

写入/etc/rc.d/rc.local 开机自动启动

echo "nohup /usr/local/bin/manager_status_check &" >> /etc/rc.d/rc.local

6.原主库加入MHA

首先修改旧主库 192.168.8.57 的参数 my.cnf，打开从库相关的参数，要重启.

方法一：由于有GTID，我们可以直接就 change master 切换过去

对比一下数据

192.168.8.57

mysql> use testReading table information for completion of table and column namesYou can turn off this feature to get a quicker startup with -ADatabase changedmysql> show tables;+----------------+| Tables_in_test |+----------------+| t1             || t2             || t3             || t4             || t5             || t6             |+----------------+

192.168.8.58

mysql> show tables;+----------------+| Tables_in_test |+----------------+| t1             || t2             || t3             || t4             || t5             || t6             || t7             |+----------------+

旧主库直接 change master to

mysql> change master to    -> master_host='192.168.8.58',    -> master_port=3306,    -> master_user='repl',    -> master_password='mysql',    -> master_auto_position=1;Query OK, 0 rows affected, 2 warnings (0.05 sec)

查看192.168.8.57slave进程状态

mysql> start slave;Query OK, 0 rows affected (0.07 sec)mysql> show slave status \G*************************** 1. row ***************************               Slave_IO_State: Waiting for master to send event                  Master_Host: 192.168.8.58                  Master_User: repl                  Master_Port: 3306                Connect_Retry: 60              Master_Log_File: mysql-bin.000010          Read_Master_Log_Pos: 912               Relay_Log_File: master-relay-bin.000007                Relay_Log_Pos: 619        Relay_Master_Log_File: mysql-bin.000010             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: 912              Relay_Log_Space: 1080              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: 0Master_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: 58                  Master_UUID: a92f70a4-d5ea-11e8-af28-080027c0450f             Master_Info_File: /mysql/data/master.info                    SQL_Delay: 0          SQL_Remaining_Delay: NULL      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates           Master_Retry_Count: 86400                  Master_Bind:       Last_IO_Error_Timestamp:      Last_SQL_Error_Timestamp:                Master_SSL_Crl:            Master_SSL_Crlpath:            Retrieved_Gtid_Set: a92f70a4-d5ea-11e8-af28-080027c0450f:1-5            Executed_Gtid_Set: a92f70a4-d5ea-11e8-af28-080027c0450d:1-9,a92f70a4-d5ea-11e8-af28-080027c0450f:1-5                Auto_Position: 1         Replicate_Rewrite_DB:                  Channel_Name:            Master_TLS_Version: 1 row in set (0.00 sec)

可以看到slave进程已经启动，新的主库为192.168.8.58

设置192.168.8.57参数read_only=1

mysql> set global read_only=1;Query OK, 0 rows affected (0.00 sec)mysql> show variables like 'read_only';+---------------+-------+| Variable_name | Value |+---------------+-------+| read_only     | ON    |+---------------+-------+

查看192.168.8.57数据复制情况

mysql> show tables;+----------------+| Tables_in_test |+----------------+| t1             || t2             || t3             || t4             || t5             || t6             || t7             |+----------------+

可以看到此时t7已经复制成功。

方法二：

若修复原主库耗费时间较长，建议重新初始化192.168.8.57从库，而非使用change master to

7.修改MHA配置文件

此时发现MHA配置文件app1.cnf出现缺失

[server default]manager_log=/var/log/masterha/app1/manager.logmanager_workdir=/var/log/masterha/app1master_binlog_dir=/mysql/datamaster_ip_failover_script=/usr/local/bin/master_ip_failovermaster_ip_online_change_script=/usr/local/bin/master_ip_online_changepassword=mysqlping_interval=1remote_workdir=/tmprepl_password=mysqlrepl_user=replreport_script=/usr/local/bin/send_reportsecondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.8.58 -s 192.168.8.59shutdown_script=""ssh_user=rootuser=root[server2]candidate_master=1check_repl_delay=0hostname=192.168.8.58port=3306[server3]hostname=192.168.8.59port=3306

完善之后如下：

[server default]manager_log=/var/log/masterha/app1/manager.logmanager_workdir=/var/log/masterha/app1master_binlog_dir=/mysql/datamaster_ip_failover_script=/usr/local/bin/master_ip_failovermaster_ip_online_change_script=/usr/local/bin/master_ip_online_changepassword=mysqlping_interval=1remote_workdir=/tmprepl_password=mysqlrepl_user=replreport_script=/usr/local/bin/send_reportsecondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.8.57 -s 192.168.8.59shutdown_script=""ssh_user=rootuser=root[server1]candidate_master=1check_repl_delay=0hostname=192.168.8.57port=3306[server2]hostname=192.168.8.58port=3306[server3]hostname=192.168.8.59port=3306

8.重启监控程序

MHA复制健康检查

./masterha_check_repl --conf=/etc/masterha/app1.cnfThu Oct 25 20:32:04 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Thu Oct 25 20:32:04 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..Thu Oct 25 20:32:04 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..Thu Oct 25 20:32:04 2018 - [info] MHA::MasterMonitor version 0.58.Thu Oct 25 20:32:05 2018 - [info] GTID failover mode = 1Thu Oct 25 20:32:05 2018 - [info] Dead Servers:Thu Oct 25 20:32:05 2018 - [info] Alive Servers:Thu Oct 25 20:32:05 2018 - [info]   192.168.8.57(192.168.8.57:3306)Thu Oct 25 20:32:05 2018 - [info]   192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:32:05 2018 - [info]   192.168.8.59(192.168.8.59:3306)Thu Oct 25 20:32:05 2018 - [info] Alive Slaves:Thu Oct 25 20:32:05 2018 - [info]   192.168.8.57(192.168.8.57:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 20:32:05 2018 - [info]     GTID ONThu Oct 25 20:32:05 2018 - [info]     Replicating from 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:32:05 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 20:32:05 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 20:32:05 2018 - [info]     GTID ONThu Oct 25 20:32:05 2018 - [info]     Replicating from 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:32:05 2018 - [info] Current Alive Master: 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:32:05 2018 - [info] Checking slave configurations..Thu Oct 25 20:32:05 2018 - [info] Checking replication filtering settings..Thu Oct 25 20:32:05 2018 - [info]  binlog_do_db= , binlog_ignore_db= Thu Oct 25 20:32:05 2018 - [info]  Replication filtering check ok.Thu Oct 25 20:32:05 2018 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.Thu Oct 25 20:32:05 2018 - [info] Checking SSH publickey authentication settings on the current master..Thu Oct 25 20:32:05 2018 - [info] HealthCheck: SSH to 192.168.8.58 is reachable.Thu Oct 25 20:32:05 2018 - [info] 192.168.8.58(192.168.8.58:3306) (current master) +--192.168.8.57(192.168.8.57:3306) +--192.168.8.59(192.168.8.59:3306)Thu Oct 25 20:32:05 2018 - [info] Checking replication health on 192.168.8.57..Thu Oct 25 20:32:05 2018 - [info]  ok.Thu Oct 25 20:32:05 2018 - [info] Checking replication health on 192.168.8.59..Thu Oct 25 20:32:05 2018 - [info]  ok.Thu Oct 25 20:32:05 2018 - [info] Checking master_ip_failover_script status:Thu Oct 25 20:32:05 2018 - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.8.58 --orig_master_ip=192.168.8.58 --orig_master_port=3306 Thu Oct 25 20:32:06 2018 - [info]  OK.Thu Oct 25 20:32:06 2018 - [warning] shutdown_script is not defined.Thu Oct 25 20:32:06 2018 - [info] Got exit code 0 (Not master dead).MySQL Replication Health is OK.

启动MHA监控程序

./masterha_start.sh

查看manager日志

Thu Oct 25 20:33:07 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Thu Oct 25 20:33:07 2018 - [info] Reading application default configuration from /etc/masterha/app1.cnf..Thu Oct 25 20:33:07 2018 - [info] Reading server configuration from /etc/masterha/app1.cnf..Thu Oct 25 20:33:07 2018 - [info] MHA::MasterMonitor version 0.58.Thu Oct 25 20:33:09 2018 - [info] GTID failover mode = 1Thu Oct 25 20:33:09 2018 - [info] Dead Servers:Thu Oct 25 20:33:09 2018 - [info] Alive Servers:Thu Oct 25 20:33:09 2018 - [info]   192.168.8.57(192.168.8.57:3306)Thu Oct 25 20:33:09 2018 - [info]   192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:33:09 2018 - [info]   192.168.8.59(192.168.8.59:3306)Thu Oct 25 20:33:09 2018 - [info] Alive Slaves:Thu Oct 25 20:33:09 2018 - [info]   192.168.8.57(192.168.8.57:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 20:33:09 2018 - [info]     GTID ONThu Oct 25 20:33:09 2018 - [info]     Replicating from 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:33:09 2018 - [info]     Primary candidate for the new Master (candidate_master is set)Thu Oct 25 20:33:09 2018 - [info]   192.168.8.59(192.168.8.59:3306)  Version=5.7.23-log (oldest major version between slaves) log-bin:enabledThu Oct 25 20:33:09 2018 - [info]     GTID ONThu Oct 25 20:33:09 2018 - [info]     Replicating from 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:33:09 2018 - [info] Current Alive Master: 192.168.8.58(192.168.8.58:3306)Thu Oct 25 20:33:09 2018 - [info] Checking slave configurations..Thu Oct 25 20:33:09 2018 - [info] Checking replication filtering settings..Thu Oct 25 20:33:09 2018 - [info]  binlog_do_db= , binlog_ignore_db= Thu Oct 25 20:33:09 2018 - [info]  Replication filtering check ok.Thu Oct 25 20:33:09 2018 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.Thu Oct 25 20:33:09 2018 - [info] Checking SSH publickey authentication settings on the current master..Thu Oct 25 20:33:09 2018 - [info] HealthCheck: SSH to 192.168.8.58 is reachable.Thu Oct 25 20:33:09 2018 - [info] 192.168.8.58(192.168.8.58:3306) (current master) +--192.168.8.57(192.168.8.57:3306) +--192.168.8.59(192.168.8.59:3306)Thu Oct 25 20:33:09 2018 - [info] Checking master_ip_failover_script status:Thu Oct 25 20:33:09 2018 - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.8.58 --orig_master_ip=192.168.8.58 --orig_master_port=3306 Thu Oct 25 20:33:09 2018 - [info]  OK.Thu Oct 25 20:33:09 2018 - [warning] shutdown_script is not defined.Thu Oct 25 20:33:09 2018 - [info] Set master ping interval 1 seconds.Thu Oct 25 20:33:09 2018 - [info] Set secondary check script: /usr/local/bin/masterha_secondary_check -s 192.168.8.57 -s 192.168.8.59Thu Oct 25 20:33:09 2018 - [info] Starting ping health check on 192.168.8.58(192.168.8.58:3306)..Thu Oct 25 20:33:09 2018 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

到此，自动切换及恢复工作测试完毕。

感谢各位的阅读，以上就是"MySQL5.7一主两从MHA自动切换"的内容了，经过本文的学习后，相信大家对MySQL5.7一主两从MHA自动切换这一问题有了更深刻的体会，具体使用情况还需要大家实践验证。这里是，小编将为大家推送更多相关知识点的文章，欢迎关注！