MHA学习

已于 2022-07-13 08:54:25 修改
阅读量463 收藏
点赞数
分类专栏： mysql 文章标签： 大数据
于 2022-07-12 15:07:40 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/Jiangcary/article/details/125742934
版权

目录

1、mysql架构

2、mha软件

3、mha配置文件

4、核心脚本

5、切换日志

1、mysql架构

mysql至少一主一从，一般设置为一主两从，且binlog日志目录一定要一致


2、mha软件

一个mha manager管理节点和三个node节点托管mysql实例，管理节点需单独启动，node节点不需要


3、mha配置文件

mha manager配置文件app1.cnf配置 一般存储在/etc/mastermha/下


4、核心脚本

在主库上绑定vip，通过2个脚本管理，一个是故障自动切换的脚本 master_ip_failover，一个是手动切换脚本 master_ip_online_change，vip依赖脚本漂移

5、切换日志

 5.1 手动切换

[root@Kary0 bin]# masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.56.21 --new_master_port=3306 --orig_master_is_new_slave

输出日志：
Tue Jul 12 14:41:37 2022 - [info] MHA::MasterRotate version 0.58.
Tue Jul 12 14:41:37 2022 - [info] Starting online master switch..
Tue Jul 12 14:41:37 2022 - [info] 
Tue Jul 12 14:41:37 2022 - [info] * Phase 1: Configuration Check Phase..
Tue Jul 12 14:41:37 2022 - [info] 
Tue Jul 12 14:41:37 2022 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jul 12 14:41:37 2022 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Jul 12 14:41:37 2022 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Tue Jul 12 14:41:37 2022 - [info] GTID failover mode = 0
Tue Jul 12 14:41:37 2022 - [info] Current Alive Master: 192.168.56.20(192.168.56.20:3306)
Tue Jul 12 14:41:37 2022 - [info] Alive Slaves:
Tue Jul 12 14:41:37 2022 - [info]   192.168.56.21(192.168.56.21:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 14:41:37 2022 - [info]     Replicating from 192.168.56.20(192.168.56.20:3306)
Tue Jul 12 14:41:37 2022 - [info]   192.168.56.22(192.168.56.22:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 14:41:37 2022 - [info]     Replicating from 192.168.56.20(192.168.56.20: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.56.20(192.168.56.20:3306)? (YES/no): yes

FLUSH NO_WRITE_TO_BINLOG TABLES 关闭所有打开的表，强制关闭所有正在使用的表，不写入binlog，比flush tables方式更柔和


Tue Jul 12 14:41:59 2022 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Tue Jul 12 14:41:59 2022 - [info]  ok.
Tue Jul 12 14:41:59 2022 - [info] Checking MHA is not monitoring or doing failover..
Tue Jul 12 14:41:59 2022 - [info] Checking replication health on 192.168.56.21..
Tue Jul 12 14:41:59 2022 - [info]  ok.
Tue Jul 12 14:41:59 2022 - [info] Checking replication health on 192.168.56.22..
Tue Jul 12 14:41:59 2022 - [info]  ok.
Tue Jul 12 14:41:59 2022 - [info] 192.168.56.21 can be new master.
Tue Jul 12 14:41:59 2022 - [info] 
From:
192.168.56.20(192.168.56.20:3306) (current master) 老主库
 +--192.168.56.21(192.168.56.21:3306) slave节点
 +--192.168.56.22(192.168.56.22:3306) slave节点

To:
192.168.56.21(192.168.56.21:3306) (new master) 新主库
 +--192.168.56.22(192.168.56.22:3306) slave节点
 +--192.168.56.20(192.168.56.20:3306) slave节点

Starting master switch from 192.168.56.20(192.168.56.20:3306) to 192.168.56.21(192.168.56.21:3306)? (yes/NO): yes 确认新主库


Tue Jul 12 14:42:13 2022 - [info] Checking whether 192.168.56.21(192.168.56.21:3306) is ok for the new master.. 检查老主库是否正常
Tue Jul 12 14:42:13 2022 - [info]  ok.
Tue Jul 12 14:42:13 2022 - [info] 192.168.56.20(192.168.56.20:3306): SHOW SLAVE STATUS returned empty result. To check replication filtering rules, temporarily executing CHANGE MASTER to a dummy host. 检查老主库是否上游有主库
Tue Jul 12 14:42:13 2022 - [info] 192.168.56.20(192.168.56.20:3306): Resetting slave pointing to the dummy host.
Tue Jul 12 14:42:13 2022 - [info] ** Phase 1: Configuration Check Phase completed.
Tue Jul 12 14:42:13 2022 - [info] 配置检查完成
Tue Jul 12 14:42:13 2022 - [info] * Phase 2: Rejecting updates Phase..
Tue Jul 12 14:42:13 2022 - [info] 
master_ip_online_change_script is not defined. If you do not disable writes on the current master manually, applications keep writing on the current master. Is it ok to proceed? (yes/NO): yes
Tue Jul 12 14:42:38 2022 - [info] Locking all tables on the orig master to reject updates from everybody (including root):老主库要阻塞写
Tue Jul 12 14:42:38 2022 - [info] Executing FLUSH TABLES WITH READ LOCK..
Tue Jul 12 14:42:38 2022 - [info]  ok.
Tue Jul 12 14:42:38 2022 - [info] Orig master binlog:pos is mysql-bin.000003:597.
Tue Jul 12 14:42:38 2022 - [info]  Waiting to execute all relay logs on 192.168.56.21(192.168.56.21:3306)..等待所有的中继日志在新主应用完
Tue Jul 12 14:42:38 2022 - [info]  master_pos_wait(mysql-bin.000003:597) completed on 192.168.56.21(192.168.56.21:3306). Executed 0 events.
Tue Jul 12 14:42:38 2022 - [info]   done.
Tue Jul 12 14:42:38 2022 - [info] Getting new master's binlog name and position..获取新主位点
Tue Jul 12 14:42:38 2022 - [info]  mysql-bin.000002:154 位点
Tue Jul 12 14:42:38 2022 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.56.21', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=154, MASTER_USER='root', MASTER_PASSWORD='xxx';  确认新主位点，重新同步新主
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info] * Switching slaves in parallel..
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info] -- Slave switch on host 192.168.56.22(192.168.56.22:3306) started, pid: 12172  
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info] Log messages from 192.168.56.22 ...
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info]  Waiting to execute all relay logs on 192.168.56.22(192.168.56.22:3306)..等待应用完中集继日志
Tue Jul 12 14:42:38 2022 - [info]  master_pos_wait(mysql-bin.000003:597) completed on 192.168.56.22(192.168.56.22:3306). Executed 0 events.
Tue Jul 12 14:42:38 2022 - [info]   done.
Tue Jul 12 14:42:38 2022 - [info]  Resetting slave 192.168.56.22(192.168.56.22:3306) and starting replication from the new master 192.168.56.21(192.168.56.21:3306)..
Tue Jul 12 14:42:38 2022 - [info]  Executed CHANGE MASTER. 同步到新主
Tue Jul 12 14:42:38 2022 - [info]  Slave started.
Tue Jul 12 14:42:38 2022 - [info] End of log messages from 192.168.56.22 ...
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info] -- Slave switch on host 192.168.56.22(192.168.56.22:3306) succeeded.
Tue Jul 12 14:42:38 2022 - [info] Unlocking all tables on the orig master:
Tue Jul 12 14:42:38 2022 - [info] Executing UNLOCK TABLES..老主库解锁
Tue Jul 12 14:42:38 2022 - [info]  ok.
Tue Jul 12 14:42:38 2022 - [info] Starting orig master as a new slave..老主降为slave
Tue Jul 12 14:42:38 2022 - [info]  Resetting slave 192.168.56.20(192.168.56.20:3306) and starting replication from the new master 192.168.56.21(192.168.56.21:3306)..
Tue Jul 12 14:42:38 2022 - [info]  Executed CHANGE MASTER.同步到新主
Tue Jul 12 14:42:38 2022 - [info]  Slave started.
Tue Jul 12 14:42:38 2022 - [info] All new slave servers switched successfully. 所有slave切换成功
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info] * Phase 5: New master cleanup phase..
Tue Jul 12 14:42:38 2022 - [info] 
Tue Jul 12 14:42:38 2022 - [info]  192.168.56.21: Resetting slave info succeeded.
Tue Jul 12 14:42:38 2022 - [info] Switching master to 192.168.56.21(192.168.56.21:3306) completed successfully.

5.2 故障切换

日志

[root@Kary0 masterha]# tail -f /etc/masterha/app1.log 

Tue Jul 12 16:49:40 2022 - [info] Checking master_ip_failover_script status:
Tue Jul 12 16:49:40 2022 - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.56.21 --orig_master_ip=192.168.56.21 --orig_master_port=3306 
Checking the Status of the script.. OK 
Tue Jul 12 16:49:40 2022 - [info]  OK.
Tue Jul 12 16:49:40 2022 - [warning] shutdown_script is not defined.
Tue Jul 12 16:49:40 2022 - [info] Set master ping interval 1 seconds.
Tue Jul 12 16:49:40 2022 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Tue Jul 12 16:49:40 2022 - [info] Starting ping health check on 192.168.56.21(192.168.56.21:3306)..
Tue Jul 12 16:49:40 2022 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

开始切换：
Tue Jul 12 16:50:53 2022 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away) 发现无法连接
Tue Jul 12 16:50:53 2022 - [info] Executing SSH check script: save_binary_logs --command=test --start_pos=4 --binlog_dir=/usr/local/mysql/data --output_file=/tmp/save_binary_logs_test --manager_version=0.58 --binlog_prefix=mysql-bin
Tue Jul 12 16:50:54 2022 - [info] HealthCheck: SSH to 192.168.56.21 is reachable.
Tue Jul 12 16:50:54 2022 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.21' (111)) 一次探活
Tue Jul 12 16:50:54 2022 - [warning] Connection failed 2 time(s)..
Tue Jul 12 16:50:55 2022 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.21' (111)) 二次探活
Tue Jul 12 16:50:55 2022 - [warning] Connection failed 3 time(s)..
Tue Jul 12 16:50:56 2022 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '192.168.56.21' (111)) 三次探活
Tue Jul 12 16:50:56 2022 - [warning] Connection failed 4 time(s)..
Tue Jul 12 16:50:56 2022 - [warning] Master is not reachable from health checker!
Tue Jul 12 16:50:56 2022 - [warning] Master 192.168.56.21(192.168.56.21:3306) is not reachable!
Tue Jul 12 16:50:56 2022 - [warning] SSH is reachable.
Tue Jul 12 16:50:56 2022 - [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..
Tue Jul 12 16:50:56 2022 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jul 12 16:50:56 2022 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Jul 12 16:50:56 2022 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Tue Jul 12 16:50:56 2022 - [info] GTID failover mode = 0
Tue Jul 12 16:50:56 2022 - [info] Dead Servers:
Tue Jul 12 16:50:56 2022 - [info]   192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:56 2022 - [info] Alive Servers:
Tue Jul 12 16:50:56 2022 - [info]   192.168.56.20(192.168.56.20:3306)
Tue Jul 12 16:50:56 2022 - [info]   192.168.56.22(192.168.56.22:3306)
Tue Jul 12 16:50:56 2022 - [info] Alive Slaves:
Tue Jul 12 16:50:56 2022 - [info]   192.168.56.20(192.168.56.20:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:56 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:56 2022 - [info]   192.168.56.22(192.168.56.22:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:56 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:56 2022 - [info] Checking slave configurations..
Tue Jul 12 16:50:56 2022 - [info]  read_only=1 is not set on slave 192.168.56.22(192.168.56.22:3306).
Tue Jul 12 16:50:56 2022 - [warning]  relay_log_purge=0 is not set on slave 192.168.56.22(192.168.56.22:3306).
Tue Jul 12 16:50:56 2022 - [info] Checking replication filtering settings..
Tue Jul 12 16:50:56 2022 - [info]  Replication filtering check ok.
Tue Jul 12 16:50:56 2022 - [info] Master is down!
Tue Jul 12 16:50:56 2022 - [info] Terminating monitoring script.
Tue Jul 12 16:50:56 2022 - [info] Got exit code 20 (Master dead).
Tue Jul 12 16:50:56 2022 - [info] MHA::MasterFailover version 0.58.
Tue Jul 12 16:50:56 2022 - [info] Starting master failover.
Tue Jul 12 16:50:56 2022 - [info] 
Tue Jul 12 16:50:56 2022 - [info] * Phase 1: Configuration Check Phase..
Tue Jul 12 16:50:56 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] GTID failover mode = 0
Tue Jul 12 16:50:57 2022 - [info] Dead Servers:
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info] Checking master reachability via MySQL(double check)...
Tue Jul 12 16:50:57 2022 - [info]  ok.
Tue Jul 12 16:50:57 2022 - [info] Alive Servers:
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.20(192.168.56.20:3306)
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.22(192.168.56.22:3306)
Tue Jul 12 16:50:57 2022 - [info] Alive Slaves:
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.20(192.168.56.20:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.22(192.168.56.22:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info] Starting Non-GTID based failover.
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] ** Phase 1: Configuration Check Phase completed.
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] * Phase 2: Dead Master Shutdown Phase..
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] Forcing shutdown so that applications never connect to the current master..
Tue Jul 12 16:50:57 2022 - [info] Executing master IP deactivation script:
Tue Jul 12 16:50:57 2022 - [info]   /usr/local/bin/master_ip_failover --orig_master_host=192.168.56.21 --orig_master_ip=192.168.56.21 --orig_master_port=3306 --command=stopssh --ssh_user=root  
Disabling the VIP on old master: 192.168.56.21 
Tue Jul 12 16:50:57 2022 - [info]  done.
Tue Jul 12 16:50:57 2022 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Tue Jul 12 16:50:57 2022 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] * Phase 3: Master Recovery Phase..
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] The latest binary log file/position on all slaves is mysql-bin.000003:154
Tue Jul 12 16:50:57 2022 - [info] Latest slaves (Slaves that received relay log files to the latest):
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.20(192.168.56.20:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.22(192.168.56.22:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info] The oldest binary log file/position on all slaves is mysql-bin.000003:154
Tue Jul 12 16:50:57 2022 - [info] Oldest slaves:
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.20(192.168.56.20:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info]   192.168.56.22(192.168.56.22:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jul 12 16:50:57 2022 - [info]     Replicating from 192.168.56.21(192.168.56.21:3306)
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
Tue Jul 12 16:50:57 2022 - [info] 
Tue Jul 12 16:50:57 2022 - [info] Fetching dead master's binary logs..
Tue Jul 12 16:50:57 2022 - [info] Executing command on the dead master 192.168.56.21(192.168.56.21:3306): save_binary_logs --command=save --start_file=mysql-bin.000003  --start_pos=154 --binlog_dir=/usr/local/mysql/data --output_file=/tmp/saved_master_binlog_from_192.168.56.21_3306_20220712165056.binlog --handle_raw_binlog=1 --disable_log_bin=0 --manager_version=0.58
  Creating /tmp if not exists..    ok.
 Concat binary/relay logs from mysql-bin.000003 pos 154 to mysql-bin.000003 EOF into /tmp/saved_master_binlog_from_192.168.56.21_3306_20220712165056.binlog ..
 Binlog Checksum enabled
  Dumping binlog format description event, from position 0 to 154.. ok.
  No need to dump effective binlog data from /usr/local/mysql/data/mysql-bin.000003 (pos starts 154, filesize 154). Skipping.
 Binlog Checksum enabled
 /tmp/saved_master_binlog_from_192.168.56.21_3306_20220712165056.binlog has no effective data events.
Event not exists.
Tue Jul 12 16:50:58 2022 - [info] Additional events were not found from the orig master. No need to save.
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info] * Phase 3.3: Determining New Master Phase..
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info] Finding the latest slave that has all relay logs for recovering other slaves..
Tue Jul 12 16:50:58 2022 - [info] All slaves received relay logs to the same position. No need to resync each other.
Tue Jul 12 16:50:58 2022 - [info] Searching new master from slaves..
Tue Jul 12 16:50:58 2022 - [info]  Candidate masters from the configuration file:
Tue Jul 12 16:50:58 2022 - [info]  Non-candidate masters:
Tue Jul 12 16:50:58 2022 - [info] New master is 192.168.56.20(192.168.56.20:3306)
Tue Jul 12 16:50:58 2022 - [info] Starting master failover..
Tue Jul 12 16:50:58 2022 - [info] 
From:
192.168.56.21(192.168.56.21:3306) (current master)
 +--192.168.56.20(192.168.56.20:3306)
 +--192.168.56.22(192.168.56.22:3306)

To:
192.168.56.20(192.168.56.20:3306) (new master)
 +--192.168.56.22(192.168.56.22:3306)
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info] * Phase 3.4: New Master Diff Log Generation Phase..
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info] * Phase 3.5: Master Log Apply Phase..
Tue Jul 12 16:50:58 2022 - [info] 
Tue Jul 12 16:50:58 2022 - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
Tue Jul 12 16:50:58 2022 - [info] Starting recovery on 192.168.56.20(192.168.56.20:3306)..
Tue Jul 12 16:50:58 2022 - [info]  This server has all relay logs. Waiting all logs to be applied.. 
Tue Jul 12 16:50:58 2022 - [info]   done.
Tue Jul 12 16:50:58 2022 - [info]  All relay logs were successfully applied.
Tue Jul 12 16:50:58 2022 - [info] Getting new master's binlog name and position..
Tue Jul 12 16:50:58 2022 - [info]  mysql-bin.000003:597
Tue Jul 12 16:50:58 2022 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.56.20', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000003', MASTER_LOG_POS=597, MASTER_USER='root', MASTER_PASSWORD='xxx';
Tue Jul 12 16:50:58 2022 - [info] Executing master IP activate script:
Tue Jul 12 16:50:58 2022 - [info]   /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.56.21 --orig_master_ip=192.168.56.21 --orig_master_port=3306 --new_master_host=192.168.56.20 --new_master_ip=192.168.56.20 --new_master_port=3306 --new_master_user='root'   --new_master_password=xxx
Unknown option: new_master_user
Unknown option: new_master_password
Enabling the VIP - 192.168.100.100 on the new master - 192.168.56.20 
Tue Jul 12 16:51:02 2022 - [info]  OK.
Tue Jul 12 16:51:02 2022 - [info] Setting read_only=0 on 192.168.56.20(192.168.56.20:3306)..
Tue Jul 12 16:51:02 2022 - [info]  ok.
Tue Jul 12 16:51:02 2022 - [info] ** Finished master recovery successfully.
Tue Jul 12 16:51:02 2022 - [info] * Phase 3: Master Recovery Phase completed.
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] * Phase 4: Slaves Recovery Phase..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] -- Slave diff file generation on host 192.168.56.22(192.168.56.22:3306) started, pid: 20891. Check tmp log /etc/masterha//192.168.56.22_3306_20220712165056.log if it takes time..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] Log messages from 192.168.56.22 ...
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
Tue Jul 12 16:51:02 2022 - [info] End of log messages from 192.168.56.22.
Tue Jul 12 16:51:02 2022 - [info] -- 192.168.56.22(192.168.56.22:3306) has the latest relay log events.
Tue Jul 12 16:51:02 2022 - [info] Generating relay diff files from the latest slave succeeded.
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] -- Slave recovery on host 192.168.56.22(192.168.56.22:3306) started, pid: 20893. Check tmp log /etc/masterha//192.168.56.22_3306_20220712165056.log if it takes time..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] Log messages from 192.168.56.22 ...
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] Starting recovery on 192.168.56.22(192.168.56.22:3306)..
Tue Jul 12 16:51:02 2022 - [info]  This server has all relay logs. Waiting all logs to be applied.. 
Tue Jul 12 16:51:02 2022 - [info]   done.
Tue Jul 12 16:51:02 2022 - [info]  All relay logs were successfully applied.
Tue Jul 12 16:51:02 2022 - [info]  Resetting slave 192.168.56.22(192.168.56.22:3306) and starting replication from the new master 192.168.56.20(192.168.56.20:3306)..
Tue Jul 12 16:51:02 2022 - [info]  Executed CHANGE MASTER.
Tue Jul 12 16:51:02 2022 - [info]  Slave started.
Tue Jul 12 16:51:02 2022 - [info] End of log messages from 192.168.56.22.
Tue Jul 12 16:51:02 2022 - [info] -- Slave recovery on host 192.168.56.22(192.168.56.22:3306) succeeded.
Tue Jul 12 16:51:02 2022 - [info] All new slave servers recovered successfully.
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] * Phase 5: New master cleanup phase..
Tue Jul 12 16:51:02 2022 - [info] 
Tue Jul 12 16:51:02 2022 - [info] Resetting slave info on the new master..
Tue Jul 12 16:51:02 2022 - [info]  192.168.56.20: Resetting slave info succeeded.
Tue Jul 12 16:51:02 2022 - [info] Master failover to 192.168.56.20(192.168.56.20:3306) completed successfully.
Tue Jul 12 16:51:02 2022 - [info] Deleted server02 entry from /etc/masterha/app1.cnf .
Tue Jul 12 16:51:02 2022 - [info] 

----- Failover Report -----

app1: MySQL Master failover 192.168.56.21(192.168.56.21:3306) to 192.168.56.20(192.168.56.20:3306) succeeded

Master 192.168.56.21(192.168.56.21:3306) is down!

Check MHA Manager logs at Kary0.com:/etc/masterha/app1.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.56.21(192.168.56.21:3306)
The latest slave 192.168.56.20(192.168.56.20:3306) has all relay logs for recovery.
Selected 192.168.56.20(192.168.56.20:3306) as a new master.
192.168.56.20(192.168.56.20:3306): OK: Applying all logs succeeded.
192.168.56.20(192.168.56.20:3306): OK: Activated master IP address.
192.168.56.22(192.168.56.22:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.56.22(192.168.56.22:3306): OK: Applying all logs succeeded. Slave started, replicating from 192.168.56.20(192.168.56.20:3306)
192.168.56.20(192.168.56.20:3306): Resetting slave info succeeded.
Master failover to 192.168.56.20(192.168.56.20:3306) completed successfully.

Jiangcary
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
mha安装文件
05-11
部署MySQL高可用的必备程序，MySQL dba必备软件 部署MySQL高可用的必备程序，MySQL dba必备软件
mha数据库集群
10-28
如果你对MHA感兴趣，可以从以下几个方面进行学习： - 阅读官方文档：了解MHA的基本概念和配置方法。 - 参考实战教程：通过实践操作，加深对MHA的理解。 - 加入社区讨论：与其他MHA用户交流经验，解决遇到的问题。 ...
医学影像数据格式转换（.mha转.jpg）
qq_45603919的博客
06-10 3437
文章目录医学影像中.mha转.jpg1. BRAST2015数据集介绍2.格式转换结果展示 医学影像中.mha转.jpg 1. BRAST2015数据集介绍 ​ BRAST2015的数据集格式如上图所示，由5个.mha文件构成。其中Flair,T2,T1c,T2为四种模态（理解为四种提取特征的方式），OT为GroundTruth也就是掩码（0，1，2，3，4五种标签）。 2.格式转换 ​ 在进行图像分割的过程中，数据集最基本的格式为图片＋掩码（图片作为数据，掩码作为真值）。故在处理医学影像时需要将.mh
mha的应用
欢迎查阅
11-13 1657
mha的高级应用1. Failover1.1 mha的failover如何实现2. 数据补偿3. mha的应用透明 VIP4. mha 故障提醒5. 额外的数据补偿（binlog_server）6. 故障模拟及恢复6.1 宕机掉数主库6.2 恢复6.2.1 启动故障节点6.2.2 恢复1主2从6.2.3恢复配置文件6.2.4 恢复binlog_server6.2.5 启动mha7. 要是想重新恢复到sjk1为主库 节点的分布 192.168.80.90 sjk1 主库 mha的node安装
MHA 配置文件样本描述
乐沙弥的世界
04-13 4645
与绝大多数Linux应用程序类似，MHA的正确使用依赖于合理的配置文件。MHA的配置文件与mysql的my.cnf文件配置相似，采取的是分模块，param=value的方式来配置，配置文件位于管理节点，通常包括每一个mysql server的主机名，mysql用户名，密码，工作目录等等。本文列出了单套MHA以及采用全局配置来管理多套MHA配置文件的一些样例，供大家参考。
mha源码包以及和mha依赖包
10-30
通过阅读和学习源码，开发者可以定制自己的MHA模块，优化故障转移性能或者增加新的功能。 总的来说，这个压缩包提供了全面了解和研究MHA的资源，对于运维人员和开发人员来说，无论是为了提升数据库的高可用性，还是...
mha4mysql-0.57
08-18
- `mha4mysql-node-0.57.tar`：包含node的源代码，同样可以进行深度学习和修改。 安装mha4mysql-0.57通常包括以下步骤： 1. 解压下载的tar文件：`tar -xvf mha4mysql-manager-0.57.tar` 和 `tar -xvf mha4mysql-...
linux运维学习笔记：MHA高可用架构原理与实战.pdf
08-18
MHA 高可用架构原理与实战 MHA（Master High Availability）是一种优秀的高可用软件，用于 MySQL 高可用环境下的故障切换和主从提升。它由日本 DeNA 公司的 youshimaton（现就职于 Facebook 公司）开发，目前在 ...
MySQL高可用学习笔记mysqlrouter_MHA.docx
08-14
MySQL 高可用学习笔记 mysqlrouter_MHA 本文档主要讲解了 MySQL Router 和 MHA 的高可用配置和测试步骤。MySQL Router 是一个提供高可用和负载均衡的工具，而 MHA 是一个提供高可用和自动failover 的工具。下面我们...
mha格式图片转为jpg格式
05-17
mha格式图片转为jpg格式, 程序用matlab写，直接运行main.m文件即可
ITK系列23_ 区域增长(置信连接)算法对脑部MHA文件进行三维分割
qq_32809093的博客
05-18 1283
实例23置信连接算法对脑部MHA文件进行三维分割 在这个例子中使用前面例子中的代码，并设置图像的维数为 3 。应用梯度各向异性扩散来平滑图像。这个滤波器使用两个迭代器、一个值为 0.05 的 time step 和一个值为 3 的conductance 值，然后使用置信连接方式对平滑后的图像进行分割。使用的五个种子点的坐标分别为（ 118 ， 85 ， 92 ）、（ 63 ， 87 ， 94 ）、（ 63 ， 157 ， 90 ）、（ 111 ， 188 ， 90 ）、（ 111 ， 50 ， 88 ）.
python通过SimpleITK库预览.mha格式图片
crazyjinks的博客
06-14 716
file_path = Path(“/Users/mark/ok.mha”) # 改为你的mha图片的路径地址。# 将SimpleITK图像转换为NumPy数组。# 使用SimpleITK库读取MHA文件。
MHA文档翻译 配置文件部分
FaN()
07-20 394
配置文件 创建application配置文件 创建global配置文件 Binlog server 创建application配置文件示例manager_host$ cat /etc/app1.cnf[server default] # mysql user and password user=root password=mysqlpass # working directory on the ma
MHA高可用配置及故障切换
AH99999的博客
03-31 1278
一套优秀的MySQL高可用环境下故障切换和主从复制的软件MHA的出现就是解决MySQL单点的问题。MySQL故障过程中，MHA能做到0-30秒内自动完成故障切换MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用。
Mysql群集MHA高可用配置
weixin_72625764的博客
01-04 972
MHA（MasterHigh Availability）是一套优秀的MySQL高可用环境下故障切换和主从复制的软件。MHA 的出现就是解决MySQL 单点的问题。MySQL故障切换过程中，MHA能做到0-30秒内自动完成故障切换操作。MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用。
MySQL MHA详解（二）——实战配置
永远是少年
01-08 1837
今天继续给大家介绍MySQL的相关知识，本文主要内容是MySQL MHA高可用的实战配置。 一、实战环境 二、软件安装 三、SSH免密登录配置 四、搭建MySQL主从同步 五、配置MHA 六、效果验证
mha格式的CT体数据转为jpg切片
代码小牛的博客
11-09 1440
mha格式的CT体数据转为jpg切片搜小说 https://shupu.org/ mha格式 .mha文件是一种体数据的存储格式，由一个描述数据的头和数据组成，一般我们拿到的原始医学影像的数据是.dcm也就是dicom文件，dicom文件很复杂包含了各种各样的标签，通常我们只关心dicom里的影像信息，所以一般会把多个dicom切片转成一个文件，例如.mha .mhd文件，这些文件里只包...
mysql高可用之mha安装配置
MssGuo的博客
11-15 1108
mysql高可用mha
大数据信用查询什么样的平台比较靠谱?
最新发布
xiaoyikj的博客
08-01 695
随着互联网的发展和普及，大数据技术逐渐应用到各行各业中，其中之一就是信用查询领域，大数据信用查询平台能够为用户提供全面、准确的大数据信用评估，然而，由于市场上出现了许多不同的大数据信用查询平台，我们如何才能选择一个靠谱可信的平台呢?市面上很查询大数据的平台都只有一个单链接，用户查询完成之后，对报告有不清楚的地方，根本没有办法找到专人为其分析，如果一份报告自己看不懂，没有人解答，那么这次的钱就是白花了，而小易大数据平台则是市面上为数不多的提供大数据报告免费解读的平台，深受用户好评。
MySQL 5.7主从部署与MHA高可用实战指南
- Drizzle：在MySQL的基础上进行了简化，删除了一些复杂功能，适用于轻量级应用和学习环境。 2. 版本管理与选择： - MySQL的版本号由3部分组成：主版本号（描述文件格式）、发行级别和具体版本号。选择版本时，应...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值