MySQL5.7一主两从MHA自动更换
发布时间：2022-01-19 09:47:45 所属栏目：MySql教程 来源：互联网
导读：这篇文章主要讲解了MySQL5.7一主两从MHA自动切换，文中的讲解内容简单清晰，易于学习与理解，下面请大家跟着小编的思路慢慢深入，一起来研究和学习MySQL5.7一主两从MHA自动切换吧！ 数据库架构：一主两从 master：192.168.8.57 slave1：192.168.8.58 slave2
|
这篇文章主要讲解了“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 ifconfig enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> 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<link> 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 0 enp0s3:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> 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<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> 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 0 virbr0: flags=4099<UP,BROADCAST,MULTICAST> 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.log Thu 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 0 Thu 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=SELECT Thu 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 = 1 Thu 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:enabled Thu Oct 25 19:34:57 2018 - [info] GTID ON Thu 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:enabled Thu Oct 25 19:34:57 2018 - [info] GTID ON Thu 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 = 1 Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:707 Thu Oct 25 19:34:58 2018 - [info] Retrieved Gtid Set: a92f70a4-d5ea-11e8-af28-080027c0450d:7-9 Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:707 Thu Oct 25 19:34:58 2018 - [info] Retrieved Gtid Set: a92f70a4-d5ea-11e8-af28-080027c0450d:7-9 Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:enabled Thu Oct 25 19:34:58 2018 - [info] GTID ON Thu 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:747 Thu 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-4 Thu 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=xxx Undefined 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:0 Thu 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) succeeded Master 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:0 192.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 G Empty 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-4 1 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 *************************** （编辑：拼字网 - 核心网） 【声明】本站内容均来自网络，其相关言论仅代表作者个人观点，不代表本站立场。若无意侵犯到您的权利，请及时与联系站长删除相关内容! |
站长推荐