【MySQL】MHA正常主从切换

于 2024-08-03 10:03:24 发布
阅读量226 收藏
点赞数 2
分类专栏： 数据库运维-MySQL 文章标签： mysql 数据库
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43346403/article/details/140886188
版权

1.主从切换 

--现在主节点是:1.12,需要把主节点切换到:1.11;

masterha_master_switch --conf=/etc/masterha/app1.cnf \
--master_state=alive --new_master_host=192.168.1.11 \
--new_master_port=3306 --orig_master_is_new_slave \
--running_updates_limit=10000

[root@mysql1 bin]# masterha_master_switch --conf=/etc/masterha/app1.cnf \
> --master_state=alive --new_master_host=192.168.1.11 \
> --new_master_port=3306 --orig_master_is_new_slave \
> --running_updates_limit=10000
Sat Aug  3 09:24:43 2024 - [info] MHA::MasterRotate version 0.58.
Sat Aug  3 09:24:43 2024 - [info] Starting online master switch..
Sat Aug  3 09:24:43 2024 - [info] 
Sat Aug  3 09:24:43 2024 - [info] * Phase 1: Configuration Check Phase..
Sat Aug  3 09:24:43 2024 - [info] 
Sat Aug  3 09:24:43 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Aug  3 09:24:43 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:24:43 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:24:44 2024 - [info] GTID failover mode = 1
Sat Aug  3 09:24:44 2024 - [info] Current Alive Master: 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:24:44 2024 - [info] Alive Slaves:
Sat Aug  3 09:24:44 2024 - [info]   192.168.1.11(192.168.1.11:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:24:44 2024 - [info]     GTID ON
Sat Aug  3 09:24:44 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:24:44 2024 - [info]     Primary candidate for the new Master (candidate_master is set)
Sat Aug  3 09:24:44 2024 - [info]   192.168.1.13(192.168.1.13:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:24:44 2024 - [info]     GTID ON
Sat Aug  3 09:24:44 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:24:44 2024 - [info]   192.168.1.14(192.168.1.14:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:24:44 2024 - [info]     GTID ON
Sat Aug  3 09:24:44 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)

It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.1.12(192.168.1.12:3306)? (YES/no): yes
Sat Aug  3 09:24:46 2024 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Sat Aug  3 09:24:46 2024 - [info]  ok.
Sat Aug  3 09:24:46 2024 - [info] Checking MHA is not monitoring or doing failover..
Sat Aug  3 09:24:46 2024 - [error][/usr/local/share/perl5/MHA/MasterRotate.pm, ln143] Getting advisory lock failed on the current master. MHA Monitor runs on the current master. Stop MHA Manager/Monitor and try again.
Sat Aug  3 09:24:46 2024 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR:  at /usr/local/bin/masterha_master_switch line 53.

--从如下这句可以看出，需要先关闭MHA master节点的监控。
Stop MHA Manager/Monitor and try again

2.关闭MHA master; 

[root@mysql1 bin]# masterha_stop --conf=/etc/masterha/app1.cnf 
Stopped app1 successfully.

3.重新切换 

Sat Aug  3 09:29:01 2024 - [info]   /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=192.168.1.12 --orig_master_ip=192.168.1.12 --orig_master_port=3306 --orig_master_user='root' --new_master_host=192.168.1.11 --new_master_ip=192.168.1.11 --new_master_port=3306 --new_master_user='root' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
"my" variable $orig_master_password masks earlier declaration in same scope at /usr/local/bin/master_ip_online_change line 42.
Sat Aug  3 09:29:01 2024 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR:  at /usr/local/bin/masterha_master_switch line 53.
Sat Aug  3 09:53:45 2024 - [info]   /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=192.168.1.12 --orig_master_ip=192.168.1.12 --orig_master_port=3306 --orig_master_user='root' --new_master_host=192.168.1.11 --new_master_ip=192.168.1.11 --new_master_port=3306 --new_master_user='root' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
Sat Aug  3 09:53:45 2024 549132 Set read_only on the new master.. ok.
Sat Aug  3 09:53:45 2024 552749 Drpping app user on the orig master..
Got Error: Undefined subroutine &main::FIXME_xxx_drop_app_user called at /usr/local/bin/master_ip_online_change line 159.
Sat Aug  3 09:52:57 2024 - [info]   /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=192.168.1.12 --orig_master_ip=192.168.1.12 --orig_master_port=3306 --orig_master_user='root' --new_master_host=192.168.1.11 --new_master_ip=192.168.1.11 --new_master_port=3306 --new_master_user='root' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
"my" variable $new_master_password masks earlier declaration in same scope at /usr/local/bin/master_ip_online_change line 45.
Sat Aug  3 09:52:58 2024 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR:  at /usr/local/bin/masterha_master_switch line 53.


--$orig_master_password 已经定义过了。
--$new_master_password 已经定义过了，删除多余的即可。
--FIXME_xxx_drop_app_user 是未定义的,删除即可。

vim /usr/local/bin/master_ip_online_change
157       $orig_master_handler->disable_log_bin_local();
158       print current_time_us() . " Drpping app user on the orig master..\n";
159       #FIXME_xxx_drop_app_user($orig_master_handler); --注释这行。

4.重新进行主从切换。


[root@mysql1 bin]# masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.1.11 --new_master_port=3306 --orig_master_is_new_slave --running_updates_limit=10000
Sat Aug  3 09:54:31 2024 - [info] MHA::MasterRotate version 0.58.
Sat Aug  3 09:54:31 2024 - [info] Starting online master switch..
Sat Aug  3 09:54:31 2024 - [info] 
Sat Aug  3 09:54:31 2024 - [info] * Phase 1: Configuration Check Phase..
Sat Aug  3 09:54:31 2024 - [info] 
Sat Aug  3 09:54:31 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Aug  3 09:54:31 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:54:31 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:54:32 2024 - [info] GTID failover mode = 1
Sat Aug  3 09:54:32 2024 - [info] Current Alive Master: 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:54:32 2024 - [info] Alive Slaves:
Sat Aug  3 09:54:32 2024 - [info]   192.168.1.11(192.168.1.11:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:54:32 2024 - [info]     GTID ON
Sat Aug  3 09:54:32 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:54:32 2024 - [info]     Primary candidate for the new Master (candidate_master is set)
Sat Aug  3 09:54:32 2024 - [info]   192.168.1.13(192.168.1.13:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:54:32 2024 - [info]     GTID ON
Sat Aug  3 09:54:32 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:54:32 2024 - [info]   192.168.1.14(192.168.1.14:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:54:32 2024 - [info]     GTID ON
Sat Aug  3 09:54:32 2024 - [info]     Replicating from 192.168.1.12(192.168.1.12:3306)

It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.1.12(192.168.1.12:3306)? (YES/no): yes
Sat Aug  3 09:54:33 2024 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Sat Aug  3 09:54:33 2024 - [info]  ok.
Sat Aug  3 09:54:33 2024 - [info] Checking MHA is not monitoring or doing failover..
Sat Aug  3 09:54:33 2024 - [info] Checking replication health on 192.168.1.11..
Sat Aug  3 09:54:33 2024 - [info]  ok.
Sat Aug  3 09:54:33 2024 - [info] Checking replication health on 192.168.1.13..
Sat Aug  3 09:54:33 2024 - [info]  ok.
Sat Aug  3 09:54:33 2024 - [info] Checking replication health on 192.168.1.14..
Sat Aug  3 09:54:33 2024 - [info]  ok.
Sat Aug  3 09:54:33 2024 - [info] 192.168.1.11 can be new master.
Sat Aug  3 09:54:33 2024 - [info] 
From:
192.168.1.12(192.168.1.12:3306) (current master)
 +--192.168.1.11(192.168.1.11:3306)
 +--192.168.1.13(192.168.1.13:3306)
 +--192.168.1.14(192.168.1.14:3306)

To:
192.168.1.11(192.168.1.11:3306) (new master)
 +--192.168.1.13(192.168.1.13:3306)
 +--192.168.1.14(192.168.1.14:3306)
 +--192.168.1.12(192.168.1.12:3306)

Starting master switch from 192.168.1.12(192.168.1.12:3306) to 192.168.1.11(192.168.1.11:3306)? (yes/NO): yes
Sat Aug  3 09:54:35 2024 - [info] Checking whether 192.168.1.11(192.168.1.11:3306) is ok for the new master..
Sat Aug  3 09:54:35 2024 - [info]  ok.
Sat Aug  3 09:54:35 2024 - [info] 192.168.1.12(192.168.1.12:3306): SHOW SLAVE STATUS returned empty result. To check replication filtering rules, temporarily executing CHANGE MASTER to a dummy host.
Sat Aug  3 09:54:35 2024 - [info] 192.168.1.12(192.168.1.12:3306): Resetting slave pointing to the dummy host.
Sat Aug  3 09:54:35 2024 - [info] ** Phase 1: Configuration Check Phase completed.
Sat Aug  3 09:54:35 2024 - [info] 
Sat Aug  3 09:54:35 2024 - [info] * Phase 2: Rejecting updates Phase..
Sat Aug  3 09:54:35 2024 - [info] 
Sat Aug  3 09:54:35 2024 - [info] Executing master ip online change script to disable write on the current master:
Sat Aug  3 09:54:35 2024 - [info]   /usr/local/bin/master_ip_online_change --command=stop --orig_master_host=192.168.1.12 --orig_master_ip=192.168.1.12 --orig_master_port=3306 --orig_master_user='root' --new_master_host=192.168.1.11 --new_master_ip=192.168.1.11 --new_master_port=3306 --new_master_user='root' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
Sat Aug  3 09:54:35 2024 517988 Set read_only on the new master.. ok.
Sat Aug  3 09:54:35 2024 521343 Drpping app user on the orig master..
Sat Aug  3 09:54:35 2024 521914 Waiting all running 3 threads are disconnected.. (max 1500 milliseconds)
{'Time' => '54556','db' => undef,'Id' => '48','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql3:49440'}
{'Time' => '54556','db' => undef,'Id' => '49','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql4:53432'}
{'Time' => '53814','db' => undef,'Id' => '56','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql1:46200'}
Sat Aug  3 09:54:36 2024 026331 Waiting all running 3 threads are disconnected.. (max 1000 milliseconds)
{'Time' => '54557','db' => undef,'Id' => '48','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql3:49440'}
{'Time' => '54557','db' => undef,'Id' => '49','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql4:53432'}
{'Time' => '53815','db' => undef,'Id' => '56','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql1:46200'}
Sat Aug  3 09:54:36 2024 529379 Waiting all running 3 threads are disconnected.. (max 500 milliseconds)
{'Time' => '54557','db' => undef,'Id' => '48','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql3:49440'}
{'Time' => '54557','db' => undef,'Id' => '49','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql4:53432'}
{'Time' => '53815','db' => undef,'Id' => '56','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql1:46200'}
Sat Aug  3 09:54:37 2024 034310 Set read_only=1 on the orig master.. ok.
Sat Aug  3 09:54:37 2024 036159 Waiting all running 3 queries are disconnected.. (max 500 milliseconds)
{'Time' => '54558','db' => undef,'Id' => '48','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql3:49440'}
{'Time' => '54558','db' => undef,'Id' => '49','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql4:53432'}
{'Time' => '53816','db' => undef,'Id' => '56','User' => 'repuser','State' => 'Master has sent all binlog to slave; waiting for more updates','Command' => 'Binlog Dump GTID','Info' => undef,'Host' => 'mysql1:46200'}
Sat Aug  3 09:54:37 2024 539212 Killing all application threads..
Sat Aug  3 09:54:37 2024 542531 done.
Sat Aug  3 09:54:37 2024 - [info]  ok.
Sat Aug  3 09:54:37 2024 - [info] Locking all tables on the orig master to reject updates from everybody (including root):
Sat Aug  3 09:54:37 2024 - [info] Executing FLUSH TABLES WITH READ LOCK..
Sat Aug  3 09:54:37 2024 - [info]  ok.
Sat Aug  3 09:54:37 2024 - [info] Orig master binlog:pos is mybinlog.000002:936.
Sat Aug  3 09:54:37 2024 - [info]  Waiting to execute all relay logs on 192.168.1.11(192.168.1.11:3306)..
Sat Aug  3 09:54:37 2024 - [info]  master_pos_wait(mybinlog.000002:936) completed on 192.168.1.11(192.168.1.11:3306). Executed 0 events.
Sat Aug  3 09:54:37 2024 - [info]   done.
Sat Aug  3 09:54:37 2024 - [info] Getting new master''s binlog name and position..
Sat Aug  3 09:54:37 2024 - [info]  mybinlog.000005:230
Sat Aug  3 09:54:37 2024 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.1.11', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repuser', MASTER_PASSWORD='xxx';
Sat Aug  3 09:54:37 2024 - [info] Executing master ip online change script to allow write on the new master:
Sat Aug  3 09:54:37 2024 - [info]   /usr/local/bin/master_ip_online_change --command=start --orig_master_host=192.168.1.12 --orig_master_ip=192.168.1.12 --orig_master_port=3306 --orig_master_user='root' --new_master_host=192.168.1.11 --new_master_ip=192.168.1.11 --new_master_port=3306 --new_master_user='root' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
Sat Aug  3 09:54:37 2024 657950 Set read_only=0 on the new master.
Sat Aug  3 09:54:37 2024 658994 Creating app user on the new master..
Got Error: Undefined subroutine &main::FIXME_xxx_create_app_user called at /usr/local/bin/master_ip_online_change line 253.

Sat Aug  3 09:54:37 2024 - [warning] Proceeding.
Sat Aug  3 09:54:37 2024 - [info] 
Sat Aug  3 09:54:37 2024 - [info] * Switching slaves in parallel..
Sat Aug  3 09:54:37 2024 - [info] 
Sat Aug  3 09:54:37 2024 - [info] -- Slave switch on host 192.168.1.13(192.168.1.13:3306) started, pid: 125757
Sat Aug  3 09:54:37 2024 - [info] 
Sat Aug  3 09:54:37 2024 - [info] -- Slave switch on host 192.168.1.14(192.168.1.14:3306) started, pid: 125758
Sat Aug  3 09:54:37 2024 - [info] 
Sat Aug  3 09:54:38 2024 - [info] Log messages from 192.168.1.14 ...
Sat Aug  3 09:54:38 2024 - [info] 
Sat Aug  3 09:54:37 2024 - [info]  Waiting to execute all relay logs on 192.168.1.14(192.168.1.14:3306)..
Sat Aug  3 09:54:37 2024 - [info]  master_pos_wait(mybinlog.000002:936) completed on 192.168.1.14(192.168.1.14:3306). Executed 0 events.
Sat Aug  3 09:54:37 2024 - [info]   done.
Sat Aug  3 09:54:37 2024 - [info]  Resetting slave 192.168.1.14(192.168.1.14:3306) and starting replication from the new master 192.168.1.11(192.168.1.11:3306)..
Sat Aug  3 09:54:37 2024 - [info]  Executed CHANGE MASTER.
Sat Aug  3 09:54:37 2024 - [info]  Slave started.
Sat Aug  3 09:54:38 2024 - [info] End of log messages from 192.168.1.14 ...
Sat Aug  3 09:54:38 2024 - [info] 
Sat Aug  3 09:54:38 2024 - [info] -- Slave switch on host 192.168.1.14(192.168.1.14:3306) succeeded.
Sat Aug  3 09:54:38 2024 - [info] Log messages from 192.168.1.13 ...
Sat Aug  3 09:54:38 2024 - [info] 
Sat Aug  3 09:54:37 2024 - [info]  Waiting to execute all relay logs on 192.168.1.13(192.168.1.13:3306)..
Sat Aug  3 09:54:37 2024 - [info]  master_pos_wait(mybinlog.000002:936) completed on 192.168.1.13(192.168.1.13:3306). Executed 0 events.
Sat Aug  3 09:54:37 2024 - [info]   done.
Sat Aug  3 09:54:37 2024 - [info]  Resetting slave 192.168.1.13(192.168.1.13:3306) and starting replication from the new master 192.168.1.11(192.168.1.11:3306)..
Sat Aug  3 09:54:37 2024 - [info]  Executed CHANGE MASTER.
Sat Aug  3 09:54:37 2024 - [info]  Slave started.
Sat Aug  3 09:54:38 2024 - [info] End of log messages from 192.168.1.13 ...
Sat Aug  3 09:54:38 2024 - [info] 
Sat Aug  3 09:54:38 2024 - [info] -- Slave switch on host 192.168.1.13(192.168.1.13:3306) succeeded.
Sat Aug  3 09:54:38 2024 - [info] Unlocking all tables on the orig master:
Sat Aug  3 09:54:38 2024 - [info] Executing UNLOCK TABLES..
Sat Aug  3 09:54:38 2024 - [info]  ok.
Sat Aug  3 09:54:38 2024 - [info] Starting orig master as a new slave..
Sat Aug  3 09:54:38 2024 - [info]  Resetting slave 192.168.1.12(192.168.1.12:3306) and starting replication from the new master 192.168.1.11(192.168.1.11:3306)..
Sat Aug  3 09:54:38 2024 - [info]  Executed CHANGE MASTER.
Sat Aug  3 09:54:39 2024 - [info]  Slave started.
Sat Aug  3 09:54:39 2024 - [info] All new slave servers switched successfully.
Sat Aug  3 09:54:39 2024 - [info] 
Sat Aug  3 09:54:39 2024 - [info] * Phase 5: New master cleanup phase..
Sat Aug  3 09:54:39 2024 - [info] 
Sat Aug  3 09:54:39 2024 - [info]  192.168.1.11: Resetting slave info succeeded.
Sat Aug  3 09:54:39 2024 - [info] Switching master to 192.168.1.11(192.168.1.11:3306) completed successfully.

5.检查切换后的主从情况 。


[root@mysql1 bin]# masterha_check_repl --conf=/etc/masterha/app1.cnf
Sat Aug  3 09:57:53 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Aug  3 09:57:53 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:57:53 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Aug  3 09:57:53 2024 - [info] MHA::MasterMonitor version 0.58.
Sat Aug  3 09:57:54 2024 - [info] GTID failover mode = 1
Sat Aug  3 09:57:54 2024 - [info] Dead Servers:
Sat Aug  3 09:57:54 2024 - [info] Alive Servers:
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.11(192.168.1.11:3306)
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.12(192.168.1.12:3306)
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.13(192.168.1.13:3306)
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.14(192.168.1.14:3306)
Sat Aug  3 09:57:54 2024 - [info] Alive Slaves:
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.12(192.168.1.12:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:57:54 2024 - [info]     GTID ON
Sat Aug  3 09:57:54 2024 - [info]     Replicating from 192.168.1.11(192.168.1.11:3306)
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.13(192.168.1.13:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:57:54 2024 - [info]     GTID ON
Sat Aug  3 09:57:54 2024 - [info]     Replicating from 192.168.1.11(192.168.1.11:3306)
Sat Aug  3 09:57:54 2024 - [info]   192.168.1.14(192.168.1.14:3306)  Version=5.7.34-log (oldest major version between slaves) log-bin:enabled
Sat Aug  3 09:57:54 2024 - [info]     GTID ON
Sat Aug  3 09:57:54 2024 - [info]     Replicating from 192.168.1.11(192.168.1.11:3306)
Sat Aug  3 09:57:54 2024 - [info] Current Alive Master: 192.168.1.11(192.168.1.11:3306)
Sat Aug  3 09:57:54 2024 - [info] Checking slave configurations..
Sat Aug  3 09:57:54 2024 - [info] Checking replication filtering settings..
Sat Aug  3 09:57:54 2024 - [info]  binlog_do_db= , binlog_ignore_db= 
Sat Aug  3 09:57:54 2024 - [info]  Replication filtering check ok.
Sat Aug  3 09:57:54 2024 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Sat Aug  3 09:57:54 2024 - [info] Checking SSH publickey authentication settings on the current master..
Sat Aug  3 09:57:54 2024 - [info] HealthCheck: SSH to 192.168.1.11 is reachable.
Sat Aug  3 09:57:54 2024 - [info] 
192.168.1.11(192.168.1.11:3306) (current master)
 +--192.168.1.12(192.168.1.12:3306)
 +--192.168.1.13(192.168.1.13:3306)
 +--192.168.1.14(192.168.1.14:3306)

Sat Aug  3 09:57:54 2024 - [info] Checking replication health on 192.168.1.12..
Sat Aug  3 09:57:54 2024 - [info]  ok.
Sat Aug  3 09:57:54 2024 - [info] Checking replication health on 192.168.1.13..
Sat Aug  3 09:57:54 2024 - [info]  ok.
Sat Aug  3 09:57:54 2024 - [info] Checking replication health on 192.168.1.14..
Sat Aug  3 09:57:54 2024 - [info]  ok.
Sat Aug  3 09:57:54 2024 - [info] Checking master_ip_failover_script status:
Sat Aug  3 09:57:54 2024 - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.1.11 --orig_master_ip=192.168.1.11 --orig_master_port=3306 
Sat Aug  3 09:57:54 2024 - [info]  OK.
Sat Aug  3 09:57:54 2024 - [warning] shutdown_script is not defined.
Sat Aug  3 09:57:54 2024 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

--由此可见1.11，现在是主了，其他三个节点是备库。

戒掉贪嗔痴(薛双奇)
关注
  • 2
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
MHA部署mysql自动切换主从
Jiang
12-23 288
关闭防火墙 systemctl stop firewalld setenforce 0 配置ssh连接 四个节点都需要做无密码连接 ssh-keygen ssh-copy-id root@192.168.181.177 ssh-copy-id root@192.168.181.178 ssh-copy-id root@192.168.181.179 测试是否连接成功 做mysql一主多从 1.部署master yum -y install mariadb mariadb-server #安装m
Mysql数据库MHA故障切换
勤能补拙，知行合一
02-21 689
文章目录前言：MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用搭建Mysql MHA先关闭防火墙 文件防护（四个机器上都要操作）配置hosts文件（四个机器上都要操作）配置主从同步切换到主服务器切换到从服务器1切换到从服务器2设置命令软链接（一主两从都要设置）在所有数据库节点进行mysql授权切换到主服务器查看位置点在slave1 ，slave2执行同步操作在所有服务器上安装 MHA依赖的环境，首先安装epel源在 MHA manager 节点上安装 manager 组件在所有
MHA实现mysql主从数据库手动切换的方法
12-15
本文实例讲述了MHA实现mysql主从数据库手动切换的方法，分享给大家供大家参考。具体方法如下： 一、准备工作 1、分别在Master和Slave执行如下,方便mha检查复制: 代码如下:grant all privileges on *.* to ‘root’@’10.1.1.231’ identified by ‘rootpass’; grant all privileges on *.* to ‘root’@’10.1.1.234’ identified by ‘rootpass’; grant replication slave on *.* to ‘jpsync’@’10.1.1.
MHA自动主从切换
别浪
05-26 441
MHA自动主从切换实战 1.下载 mha4mysql-manager wget https://github.com/yoshinorim/mha4mysql-manager/releases/download/v0.58/mha4mysql-manager-0.58-0.el7.centos.noarch.rpm 2.下载 mha4mysql-node wget https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.
MySQL案例：MHA实现主备切换（主从架构）万字详解
最新发布
变成我......
08-02 1135
Linux案例：在基于主从的架构下使用MHA来管理主备切换的示例步骤
MHA部署和切换
qq_57052445的博客
05-12 518
Master High Availability（MHA）是一种用于确保服务连续性和高可用性的解决方案，主要应用于MySQL等数据库系统。它通过监控数据库主节点的状态，当主节点出现故障时自动切换到备份节点上，并将新的主节点信息广播给其他节点，从而确保整个系统在主节点故障的情况下仍然可以正常工作。MHA的主要功能包括：自动监测：MHA会持续监测主节点的状态，并在发生故障时立即进行处理。快速故障转移：当主节点出现故障时，MHA会自动将工作负载转移到备份节点上，从而实现快速的故障转移。
基于MHA实现MySQL故障转移和主从切换
HackDaily
02-20 880
基于MHA实现Mysql高可用环境搭建手册，故障转移、主从切换、故障切换后恢复需要注意的地方。
mysql MHA脚本masterha_master_switch手动操作常见错误
u010719917的专栏
05-23 3659
Mon May 21 16:56:06 2018 - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln1261] Failed to activate master IP address for centos129 with return code 10:0解决办法：？ [warning] Got timeout on MySQL ...
MHA实现mysql8主从故障切换
qq_37369726的博客
02-23 1969
MHA介绍 MHA是mysql高可用的一个相对成熟的方案，可以实现故障切换。在mysql集群出现故障时，mha可以在短时间内自动完成数据库的故障切换，并在最大程度上保证数据的一致性。 实现故障切花的过程： 各个mysql主从之间通过ssh通信，当master宕机时，mha尝试ssh登入到宕机的机器，保存二进制日志（binlog），从多个slave中识别出含有最新更新的slave，并将其作为备选的m...
MHA实现mysql5.6主从切换安装配置教程.docx
12-24
在本教程中，我们将探讨如何在MySQL 5.6环境中使用MHA进行主从切换的安装和配置。 首先，我们需要安装MHA软件。这涉及到两个主要的组件：`mha4mysql-node` 和 `mha4mysql-manager`。通过 `yum` 命令或直接下载 `rpm...
centos7 mysql mha架构，自动切master
weixin_50663202的博客
11-13 178
环境 系统：centos7.6 数据库：5.5.60-MariaDB MHA软件版本：mha4mysql-manager-0.56 mha4mysql-node-0.56 master 192.168.92.139 slave1 192.168.92.140 slave2 192.168.92.144 manager 192.168.92.144 一、软件安装 【1】Perl的依赖模块安装 需要所有节点安装 <1>安装epel源 yum -y install e
MHA 安装与简单使用
weixin_30924239的博客
04-08 313
MHA 在过去几年一直用的比较火，特别是在在传统复制的那个年代。至从有了GTID好像我们也可以把MHA给忘记了，但是很多企业现在还是在用的比较多。每个公司的MHA玩法也不太一样，但是本质都是差不多了。下面我就带大家简单快速的搭建一个MHA玩一下，看看MHA是怎么玩的。如果要深入的了解MHA我建议去github里面看看一些官方的文档或者别人的一些博客，google一下或者bing一下就能找到了。我也...
Mysql MHA实现主从自动切换
java1_boy的博客
09-06 2387
注意 在这个安装之前如果没有安装过Mysql的主从复制，请参考这篇博文再进行以下操作：https://blog.csdn.net/java1_boy/article/details/108331303 简介 MHA（Master High Availability）是一套比较成熟的 MySQL 高可用方案，也是一款优秀的故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA能做到在30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数据的一致性，以.
MHA实现MySQL主从自动在线切换功能
OH_ON的博客
12-16 7223
利用MHA实现MySQL主从节点的在线按需自动切换功能
mysql-多主复制、负载均衡、MHA高可用及主从切换
qq_43114229的博客
01-01 940
一、mysql多主模式配置 准备三台虚拟机： server1 、server2、server3 组复制必须保证三台数据库完全一致，否则会失败 点击搭建多主模式官方文档查看 [root@server1 data]# /etc/init.d/mysqld stop 停掉数据库 Shutting down MySQL............ SUCCESS! [root@server1 ~]# cd /usr/local/mysql/data 进入mysql数据目录 [root@server1 data]
MySQL高可用之MHA切换测试（switchover & failover）
diankuozhi9810的博客
08-02 500
Preface I've installed MasterHA yesterday,Now let's test the master-slave switch and failover feature. Framework Hostname IP Port Identity OS Version MySQL V...
mysql使用MHA-7实现主从切换
橙汁Iter的博客
03-02 1287
当mysql数据库集群中master出现故障时，如果我们不手动进行master的切换，数据库就会瘫痪，这篇博客写的是利用MHA-7实现手动以及自动的主从切换 一、MySQL高可用架构之MHA简介 1.什么是MHA MHA（MasterHigh Availability）目前在MySQL高可用方面是一个相对成熟的解决方案，它由日本DeNA公司youshimaton（现就职于Facebook...
MySQL 5.7 MHA：一键部署主从切换与高可用
MHA中的主从切换是在后台自动进行的，当主节点出现问题时，MHA会根据预设策略将负载转移到备机上，同时保持业务的连续性。这种切换过程通常包括数据同步和权限转移，以确保新的主节点可以立即接管服务。 总结来说，...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值