MySQL MHA switchover在线切换过程
发表于:2024-10-25 作者:千家信息网编辑
千家信息网最后更新 2024年10月25日,1、切换过程,注意需要关闭masterha_manager[root@es3 ~]# masterha_master_switch --master_state=alive --conf=/root
千家信息网最后更新 2024年10月25日MySQL MHA switchover在线切换过程
1、切换过程,注意需要关闭masterha_manager
[root@es3 ~]# masterha_master_switch --master_state=alive --conf=/root/app1.cnf --new_master_host=es3 --orig_master_is_new_slaveTue Aug 20 10:12:02 2019 - [info] MHA::MasterRotate version 0.58.Tue Aug 20 10:12:02 2019 - [info] Starting online master switch..Tue Aug 20 10:12:02 2019 - [info] Tue Aug 20 10:12:02 2019 - [info] * Phase 1: Configuration Check Phase..Tue Aug 20 10:12:02 2019 - [info] Tue Aug 20 10:12:02 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Tue Aug 20 10:12:02 2019 - [info] Reading application default configuration from /root/app1.cnf..Tue Aug 20 10:12:02 2019 - [info] Reading server configuration from /root/app1.cnf..Tue Aug 20 10:12:03 2019 - [info] GTID failover mode = 1Tue Aug 20 10:12:03 2019 - [info] Current Alive Master: es1(192.168.56.14:3306)Tue Aug 20 10:12:03 2019 - [info] Alive Slaves:Tue Aug 20 10:12:03 2019 - [info] es2(192.168.56.15:3306) Version=5.7.24-log (oldest major version between slaves) log-bin:enabledTue Aug 20 10:12:03 2019 - [info] GTID ONTue Aug 20 10:12:03 2019 - [info] Replicating from 192.168.56.14(192.168.56.14:3306)Tue Aug 20 10:12:03 2019 - [info] es3(192.168.56.16:3306) Version=5.7.24-log (oldest major version between slaves) log-bin:enabledTue Aug 20 10:12:03 2019 - [info] GTID ONTue Aug 20 10:12:03 2019 - [info] Replicating from es1(192.168.56.14:3306)It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on es1(192.168.56.14:3306)? (YES/no): yesTue Aug 20 10:12:06 2019 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..Tue Aug 20 10:12:06 2019 - [info] ok.Tue Aug 20 10:12:06 2019 - [info] Checking MHA is not monitoring or doing failover..Tue Aug 20 10:12:06 2019 - [info] Checking replication health on es2..Tue Aug 20 10:12:06 2019 - [info] ok.Tue Aug 20 10:12:06 2019 - [info] Checking replication health on es3..Tue Aug 20 10:12:06 2019 - [info] ok.Tue Aug 20 10:12:06 2019 - [info] es3 can be new master.Tue Aug 20 10:12:06 2019 - [info] From:es1(192.168.56.14:3306) (current master) +--es2(192.168.56.15:3306) +--es3(192.168.56.16:3306)To:es3(192.168.56.16:3306) (new master) +--es2(192.168.56.15:3306) +--es1(192.168.56.14:3306)Starting master switch from es1(192.168.56.14:3306) to es3(192.168.56.16:3306)? (yes/NO): yesTue Aug 20 10:12:11 2019 - [info] Checking whether es3(192.168.56.16:3306) is ok for the new master..Tue Aug 20 10:12:11 2019 - [info] ok.Tue Aug 20 10:12:11 2019 - [info] es1(192.168.56.14:3306): SHOW SLAVE STATUS returned empty result. To check replication filtering rules, temporarily executing CHANGE MASTER to a dummy host.Tue Aug 20 10:12:11 2019 - [info] es1(192.168.56.14:3306): Resetting slave pointing to the dummy host.Tue Aug 20 10:12:11 2019 - [info] ** Phase 1: Configuration Check Phase completed.Tue Aug 20 10:12:11 2019 - [info] Tue Aug 20 10:12:11 2019 - [info] * Phase 2: Rejecting updates Phase..Tue Aug 20 10:12:11 2019 - [info] Tue Aug 20 10:12:11 2019 - [info] Executing master ip online change script to disable write on the current master:Tue Aug 20 10:12:11 2019 - [info] /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=es1 --orig_master_ip=192.168.56.14 --orig_master_port=3306 --orig_master_user='repl' --new_master_host=es3 --new_master_ip=192.168.56.16 --new_master_port=3306 --new_master_user='repl' --orig_master_ssh_user=root --new_master_ssh_user=root --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx***************************************************************Disabling the VIP - 192.168.56.191/24 on old master: es1***************************************************************Tue Aug 20 10:12:12 2019 - [info] ok.Tue Aug 20 10:12:12 2019 - [info] Locking all tables on the orig master to reject updates from everybody (including root):Tue Aug 20 10:12:12 2019 - [info] Executing FLUSH TABLES WITH READ LOCK..Tue Aug 20 10:12:12 2019 - [info] ok.Tue Aug 20 10:12:12 2019 - [info] Orig master binlog:pos is mysqlbin.000005:194.Tue Aug 20 10:12:12 2019 - [info] Waiting to execute all relay logs on es3(192.168.56.16:3306)..Tue Aug 20 10:12:12 2019 - [info] master_pos_wait(mysqlbin.000005:194) completed on es3(192.168.56.16:3306). Executed 0 events.Tue Aug 20 10:12:12 2019 - [info] done.Tue Aug 20 10:12:12 2019 - [info] Getting new master's binlog name and position..Tue Aug 20 10:12:12 2019 - [info] mysqlbin.000004:154Tue Aug 20 10:12:12 2019 - [info] All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='es3 or 192.168.56.16', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxx';Tue Aug 20 10:12:12 2019 - [info] Executing master ip online change script to allow write on the new master:Tue Aug 20 10:12:12 2019 - [info] /usr/local/bin/master_ip_online_change --command=start --orig_master_host=es1 --orig_master_ip=192.168.56.14 --orig_master_port=3306 --orig_master_user='repl' --new_master_host=es3 --new_master_ip=192.168.56.16 --new_master_port=3306 --new_master_user='repl' --orig_master_ssh_user=root --new_master_ssh_user=root --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx***************************************************************Enabling the VIP - 192.168.56.191/24 on new master: es3 ***************************************************************Tue Aug 20 10:12:13 2019 - [info] ok.Tue Aug 20 10:12:13 2019 - [info] Tue Aug 20 10:12:13 2019 - [info] * Switching slaves in parallel..Tue Aug 20 10:12:13 2019 - [info] Tue Aug 20 10:12:13 2019 - [info] -- Slave switch on host es2(192.168.56.15:3306) started, pid: 4076Tue Aug 20 10:12:13 2019 - [info] Tue Aug 20 10:12:14 2019 - [info] Log messages from es2 ...Tue Aug 20 10:12:14 2019 - [info] Tue Aug 20 10:12:13 2019 - [info] Waiting to execute all relay logs on es2(192.168.56.15:3306)..Tue Aug 20 10:12:13 2019 - [info] master_pos_wait(mysqlbin.000005:194) completed on es2(192.168.56.15:3306). Executed 0 events.Tue Aug 20 10:12:13 2019 - [info] done.Tue Aug 20 10:12:13 2019 - [info] Resetting slave es2(192.168.56.15:3306) and starting replication from the new master es3(192.168.56.16:3306)..Tue Aug 20 10:12:13 2019 - [info] Executed CHANGE MASTER.Tue Aug 20 10:12:13 2019 - [info] Slave started.Tue Aug 20 10:12:14 2019 - [info] End of log messages from es2 ...Tue Aug 20 10:12:14 2019 - [info] Tue Aug 20 10:12:14 2019 - [info] -- Slave switch on host es2(192.168.56.15:3306) succeeded.Tue Aug 20 10:12:14 2019 - [info] Unlocking all tables on the orig master:Tue Aug 20 10:12:14 2019 - [info] Executing UNLOCK TABLES..Tue Aug 20 10:12:14 2019 - [info] ok.Tue Aug 20 10:12:14 2019 - [info] Starting orig master as a new slave..Tue Aug 20 10:12:14 2019 - [info] Resetting slave es1(192.168.56.14:3306) and starting replication from the new master es3(192.168.56.16:3306)..Tue Aug 20 10:12:14 2019 - [info] Executed CHANGE MASTER.Tue Aug 20 10:12:14 2019 - [info] Slave started.Tue Aug 20 10:12:14 2019 - [info] All new slave servers switched successfully.Tue Aug 20 10:12:14 2019 - [info] Tue Aug 20 10:12:14 2019 - [info] * Phase 5: New master cleanup phase..Tue Aug 20 10:12:14 2019 - [info] Tue Aug 20 10:12:14 2019 - [info] es3: Resetting slave info succeeded.Tue Aug 20 10:12:14 2019 - [info] Switching master to es3(192.168.56.16:3306) completed successfully.[root@es3 ~]# ip addr1: lo:mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: enp0s3: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 08:00:27:ed:8b:51 brd ff:ff:ff:ff:ff:ff inet 10.0.2.15/24 brd 10.0.2.255 scope global noprefixroute dynamic enp0s3 valid_lft 84197sec preferred_lft 84197sec inet6 fe80::c377:b5dd:2937:f269/64 scope link noprefixroute valid_lft forever preferred_lft forever3: enp0s8: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 08:00:27:1f:f9:c8 brd ff:ff:ff:ff:ff:ff inet 192.168.56.16/24 brd 192.168.56.255 scope global noprefixroute dynamic enp0s8 valid_lft 1030sec preferred_lft 1030sec inet 192.168.56.191/24 brd 192.168.56.255 scope global secondary enp0s8:1 valid_lft forever preferred_lft forever inet6 fe80::90e0:253d:ab32:8ba4/64 scope link noprefixroute valid_lft forever preferred_lft forever[root@es3 ~]#
过程
切换
在线
数据库的安全要保护哪些东西
数据库安全各自的含义是什么
生产安全数据库录入
数据库的安全性及管理
数据库安全策略包含哪些
海淀数据库安全审计系统
建立农村房屋安全信息数据库
易用的数据库客户端支持安全管理
连接数据库失败ssl安全错误
数据库的锁怎样保障安全
网络技术作业答案全解
网络安全保卫总队情报
校园网络安全的作文
赢域互联网科技有限公司
国外计算机网络安全就业前景
Go数据库关联关系
国服csgo韩国服务器维护中
阿利狼网络技术有限公司怎么样
溪网络技术有限公司
职业教育软件开发
网络安全闸设备
山东省服务器品牌云空间
网络技术与基础实验报告
网络技术安全高峰论坛
网络安全最强打工人
怎么开发数据库
托数据库教程
数据库模式包括什么
c3p0数据库连接池实例
浦东新区环保网络技术定做价格
重庆读根网络技术有限公司
电气设备及软件开发
java软件开发研究生
进销存软件开发需求文档
民警网络安全宣讲
dhcp服务器mac地址
对峙2中国服务器关闭
c 软件开发工程师年薪
互联网科技发言稿
高防服务器如何辨认