MYSQL之MHA集群
阿新 • • 發佈:2018-05-18
成功 target logs return str carp etop 方案 ....
環境
manager 192.168.137.141 master1 192.168.137.144 master2 192.168.137.145 slave 192.168.137.141 vip 192.168.137.199
部署
三臺機器已安裝mysql。
百度雲:鏈接:https://pan.baidu.com/s/1an3QjoFFdqcjo5-KWRCShw 密碼:wsq9
192.168.137.141 mha4mysql-manager-0.55-0.el6.noarch.rpm mha4mysql-node-0.54-0.el6.noarch.rpm 192.168.137.144 192.168.137.145 mha4mysql-node-0.54-0.el6.noarch.rpm
依賴
鏈接:https://pan.baidu.com/s/1mTcoBiUsvATQMkM3bXJKrA 密碼:rpvq
yum install perl perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker perl-CPAN perl-DBD-MySQL
都要安裝。
主模塊1:配置集群之前SSH免密碼登錄
兩步完成ssh免密碼登錄
192.168.137.141 --> 192.168.137.144 192.168.137.141 --> 192.168.137.145 192.168.137.144 --> 192.168.137.141 192.168.137.144 --> 192.168.137.145 192.168.137.145 --> 192.168.137.141 192.168.137.145 --> 192.168.137.144 6次
主模塊2:配置集群主從復制
mysql主備部署[高可用]
master: 192.168.137.144 slave: 192.168.137.145 master: 192.168.137.144 slave: 192.168.137.141
主模塊3:manager配置
mkdir -p /etc/masterha cd /etc/masterha vim app1.cnf
app1.cnf
[server default] user=root password=lizhenghua manager_workdir=/etc/masterha manager_log=/etc/masterha/logs/manager.log remote_workdir=/etc/masterha ssh_user=root repl_user=sync repl_password=sync ping_interval=3 #master_ip_online_change_script=/etc/masterha/script/master_ip_online_change master_ip_failover_script=/etc/masterha/script/master_ip_failover #report_script=/etc/masterha/script/sendMail_report [server1] hostname=192.168.137.144 port=3306 master_binlog_dir=/usr/local/mysql/data/ candidate_master=1 [server2] hostname=192.168.137.145 port=3306 master_binlog_dir=/usr/local/mysql/data/ candidate_master=1 [server3] hostname=192.168.137.141 port=3306 master_binlog_dir=/usr/local/mysql/data/ candidate_master=1
副模塊1:檢測SSH
masterha_check_ssh --conf=/etc/masterha/app1.cnf
模塊2:檢測主從
masterha_check_repl --conf=/etc/masterha/app1.cnf
manager啟動方式
vim start.sh #!/usr/bin/bash nohup perl /root/perl5/bin/masterha_manager --conf=/etc/masterha/conf/app1.cnf &
功能測試
192.168.137.141
mysql> show slave status \G*************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.137.144 Master_User: sync Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000003 Read_Master_Log_Pos: 154 Relay_Log_File: mysql-relay-bin.000004 Relay_Log_Pos: 367 Relay_Master_Log_File: mysql-bin.000003 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: 154 Relay_Log_Space: 740 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: 0 Master_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: 144 Master_UUID: 9abbdca0-424e-11e8-a71a-000c29deb434 Master_Info_File: /usr/local/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: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
kill掉192.168.137.144機器上的mysql, 然後141開始切換master
mysql> show slave status \G*************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.137.145 Master_User: sync Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000003 Read_Master_Log_Pos: 154 Relay_Log_File: mysql-relay-bin.000002 Relay_Log_Pos: 320 Relay_Master_Log_File: mysql-bin.000003 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: 154 Relay_Log_Space: 527 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: 0 Master_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: 145 Master_UUID: 9abbdca0-424e-11e8-a71a-000c29deb433 Master_Info_File: /usr/local/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: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
manager上日誌
切換成功!
主模塊3:VIP
master_ip_failover
#!/usr/bin/env perl use strict; use warnings FATAL => ‘all‘; use Getopt::Long; my ( $command, $ssh_user, $orig_master_host, $orig_master_ip, $orig_master_port, $new_master_host, $new_master_ip, $new_master_port ); my $vip = ‘192.168.137.199/24‘; my $key = ‘0‘; my $ssh_start_vip = "/usr/sbin/ifconfig ens33:$key $vip netmask 255.255.255.0 up"; my $ssh_stop_vip = "/usr/sbin/ifconfig ens33:$key down"; GetOptions( ‘command=s‘ => \$command, ‘ssh_user=s‘ => \$ssh_user, ‘orig_master_host=s‘ => \$orig_master_host, ‘orig_master_ip=s‘ => \$orig_master_ip, ‘orig_master_port=i‘ => \$orig_master_port, ‘new_master_host=s‘ => \$new_master_host, ‘new_master_ip=s‘ => \$new_master_ip, ‘new_master_port=i‘ => \$new_master_port, ); exit &main(); sub main { print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n"; if ( $command eq "stop" || $command eq "stopssh" ) { my $exit_code = 1; eval { print "Disabling the VIP on old master: $orig_master_host \n"; &stop_vip(); $exit_code = 0; }; if ($@) { warn "Got Error: $@\n"; exit $exit_code; } exit $exit_code; } elsif ( $command eq "start" ) { my $exit_code = 10; eval { print "Enabling the VIP - $vip on the new master - $new_master_host \n"; &start_vip(); $exit_code = 0; }; if ($@) { warn $@; exit $exit_code; } exit $exit_code; } elsif ( $command eq "status" ) { print "Checking the Status of the script.. OK \n"; exit 0; } else { &usage(); exit 1; } } sub start_vip() { `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`; } sub stop_vip() { return 0 unless ($ssh_user); `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`; } sub usage { print "Usage: master_ip_failover --command=start|stop|stopssh|status --orig_master_host=host --orig_master_ip=ip --orig_master_port=port --new_master_host=host --new_master_ip=ip --new_master_port=port\n"; }
檢測VIP漂移
第一步:啟動manager
[root@localhost masterha]# ./start.sh [root@localhost masterha]# nohup: 把輸出追加到"nohup.out" 務必保證已經啟動成功(ssh,主從檢測都沒錯一般不會出問題)! start.sh裏寫了什麽? 看上面
第二步:停止master mysql(192.168.137.144)
[root@localhost masterha]# ssh [email protected] "service mysql stop" Shutting down MySQL............ SUCCESS!
看manager.log日誌
查看原來master1 192.168.137.144發現VIP已經被down掉
發現VIP漂移到了新的master2 192.168.137.145上
此時VIP切換成功!
同時查看主從切換, 按道理說現在master1 192.168.137.144上的mysql已經宕掉, slave應該連接新的master2 137.145上
漂移前查詢
mysql> show slave status \G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.137.144 Master_User: sync Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000016 Read_Master_Log_Pos: 154 Relay_Log_File: mysql-relay-bin.000002 Relay_Log_Pos: 320 Relay_Master_Log_File: mysql-bin.000016 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: 154 Relay_Log_Space: 527 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: 0 Master_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: 144 Master_UUID: 9abbdca0-424e-11e8-a71a-000c29deb434 Master_Info_File: /usr/local/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: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
漂移後查詢 mysql> show slave status \G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.137.145 Master_User: sync Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000005 Read_Master_Log_Pos: 154 Relay_Log_File: mysql-relay-bin.000002 Relay_Log_Pos: 320 Relay_Master_Log_File: mysql-bin.000005 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: 154 Relay_Log_Space: 527 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: 0 Master_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: 145 Master_UUID: 9abbdca0-424e-11e8-a71a-000c29deb433 Master_Info_File: /usr/local/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: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec)
VIP漂移正常,主從復制正常,MHA搭建成功!
報錯信息:
SSH
測試ssh報錯 [root@localhost app]# masterha_check_ssh --conf=/etc/masterha/app/app1.cnf Thu May 17 01:04:32 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Thu May 17 01:04:32 2018 - [info] Reading application default configurations from /etc/masterha/app/app1.cnf.. Thu May 17 01:04:32 2018 - [info] Reading server configurations from /etc/masterha/app/app1.cnf.. Thu May 17 01:04:32 2018 - [info] Starting SSH connection tests.. Thu May 17 01:04:33 2018 - [error][/usr/share/perl5/vendor_perl/MHA/SSHCheck.pm, ln63] Thu May 17 01:04:32 2018 - [debug] Connecting via SSH from [email protected](192.168.137.144:22) to [email protected](192.168.137.145:22).. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Thu May 17 01:04:32 2018 - [error][/usr/share/perl5/vendor_perl/MHA/SSHCheck.pm, ln111] SSH connection from [email protected](192.168.137.144:22) to [email protected](192.168.137.145:22) failed! Thu May 17 01:04:33 2018 - [error][/usr/share/perl5/vendor_perl/MHA/SSHCheck.pm, ln63] Thu May 17 01:04:32 2018 - [debug] Connecting via SSH from [email protected](192.168.137.145:22) to [email protected](192.168.137.144:22).. Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password). Thu May 17 01:04:33 2018 - [error][/usr/share/perl5/vendor_perl/MHA/SSHCheck.pm, ln111] SSH connection from [email protected](192.168.137.145:22) to [email protected](192.168.137.144:22) failed! Bizarre copy of ARRAY in scalar assignment at /usr/share/perl5/vendor_perl/Carp.pm line 182. 解決方案 三臺機器互相配置ssh免密碼認證(每臺兩次共6次) 再測 [root@localhost app]# masterha_check_ssh --conf=/etc/masterha/app/app1.cnf Thu May 17 01:12:33 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Thu May 17 01:12:33 2018 - [info] Reading application default configurations from /etc/masterha/app/app1.cnf.. Thu May 17 01:12:33 2018 - [info] Reading server configurations from /etc/masterha/app/app1.cnf.. Thu May 17 01:12:33 2018 - [info] Starting SSH connection tests.. Thu May 17 01:12:34 2018 - [debug] Thu May 17 01:12:33 2018 - [debug] Connecting via SSH from [email protected](192.168.137.144:22) to [email protected](192.168.137.145:22).. Thu May 17 01:12:34 2018 - [debug] ok. Thu May 17 01:12:35 2018 - [debug] Thu May 17 01:12:34 2018 - [debug] Connecting via SSH from [email protected](192.168.137.145:22) to [email protected](192.168.137.144:22).. Thu May 17 01:12:35 2018 - [debug] ok. Thu May 17 01:12:35 2018 - [info] All SSH connection tests passed successfully.
主從1
主主同步報錯 mysql> show slave status \G *************************** 1. row *************************** Slave_IO_State: Master_Host: 192.168.137.145 Master_User: sync Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000001 Read_Master_Log_Pos: 336 Relay_Log_File: localhost-relay-bin.000001 Relay_Log_Pos: 4 Relay_Master_Log_File: mysql-bin.000001 Slave_IO_Running: No 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: 336 Relay_Log_Space: 154 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: NULL Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 1593 Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs; these UUIDs must be different for replication to work. Last_SQL_Errno: 0 Last_SQL_Error: Replicate_Ignore_Server_Ids: Master_Server_Id: 145 Master_UUID: Master_Info_File: /usr/local/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: 180517 01:37:32 Last_SQL_Error_Timestamp: Master_SSL_Crl: Master_SSL_Crlpath: Retrieved_Gtid_Set: Executed_Gtid_Set: Auto_Position: 0 Replicate_Rewrite_DB: Channel_Name: Master_TLS_Version: 1 row in set (0.00 sec) 解決: [root@localhost .ssh]# cd /usr/local/mysql/data/ [root@localhost data]# vim auto.cnf [auto] server-uuid=9abbdca0-424e-11e8-a71a-000c29deb434 保存退出。(保證兩個mysql的uuid不一致即可)
主從2
報錯3:主從問題 [root@localhost ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf Thu May 17 21:32:15 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Thu May 17 21:32:15 2018 - [info] Reading application default configurations from /etc/masterha/app1.cnf.. Thu May 17 21:32:15 2018 - [info] Reading server configurations from /etc/masterha/app1.cnf.. Thu May 17 21:32:15 2018 - [info] MHA::MasterMonitor version 0.55. Thu May 17 21:32:15 2018 - [warning] SQL Thread is stopped(no error) on 192.168.137.144(192.168.137.144:3306) Thu May 17 21:32:15 2018 - [error][/root/perl5/lib/perl5/MHA/ServerManager.pm, ln732] Multi-master configuration is detected, but two or more masters are either writable (read-only is not set) or dead! Check configurations for details. Master configurations are as below: Master 192.168.137.145(192.168.137.145:3306), replicating from 192.168.137.144(192.168.137.144:3306) Master 192.168.137.144(192.168.137.144:3306), replicating from 192.168.137.145(192.168.137.145:3306) Thu May 17 21:32:15 2018 - [error][/root/perl5/lib/perl5/MHA/MasterMonitor.pm, ln386] Error happend on checking configurations. at /root/perl5/lib/perl5/MHA/MasterMonitor.pm line 300. Thu May 17 21:32:15 2018 - [error][/root/perl5/lib/perl5/MHA/MasterMonitor.pm, ln482] Error happened on monitoring servers. Thu May 17 21:32:15 2018 - [info] Got exit code 1 (Not master dead). MySQL Replication Health is NOT OK! [root@localhost ~]# 解決: 在每臺mysql的my.cnf下配置屬性:(主要是備機) relay-log=/usr/local/mysql/binlog/mysql-relay-bin mkdir -p /usr/local/mysql/binlog chown -R mysql:mysql /usr/local/mysql/binlog 重啟mysql。 重新配置主從: CHANGE MASTER TO MASTER_HOST=‘192.168.137.144‘,MASTER_USER=‘sync‘,MASTER_PASSWORD=‘sync‘,MASTER_LOG_FILE=‘mysql-bin.000002‘,MASTER_LOG_POS=154; 結果: [root@localhost ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf Thu May 17 21:58:11 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Thu May 17 21:58:11 2018 - [info] Reading application default configurations from /etc/masterha/app1.cnf.. Thu May 17 21:58:11 2018 - [info] Reading server configurations from /etc/masterha/app1.cnf.. Thu May 17 21:58:11 2018 - [info] MHA::MasterMonitor version 0.55. Thu May 17 21:58:11 2018 - [info] Dead Servers: Thu May 17 21:58:11 2018 - [info] Alive Servers: Thu May 17 21:58:11 2018 - [info] 192.168.137.144(192.168.137.144:3306) Thu May 17 21:58:11 2018 - [info] 192.168.137.145(192.168.137.145:3306) Thu May 17 21:58:11 2018 - [info] Alive Slaves: Thu May 17 21:58:11 2018 - [info] 192.168.137.145(192.168.137.145:3306) Version=5.7.21-log (oldest major version between slaves) log-bin:enabled Thu May 17 21:58:11 2018 - [info] Replicating from 192.168.137.144(192.168.137.144:3306) Thu May 17 21:58:11 2018 - [info] Primary candidate for the new Master (candidate_master is set) Thu May 17 21:58:11 2018 - [info] Current Alive Master: 192.168.137.144(192.168.137.144:3306) Thu May 17 21:58:11 2018 - [info] Checking slave configurations.. Thu May 17 21:58:11 2018 - [info] read_only=1 is not set on slave 192.168.137.145(192.168.137.145:3306). Thu May 17 21:58:11 2018 - [warning] relay_log_purge=0 is not set on slave 192.168.137.145(192.168.137.145:3306). Thu May 17 21:58:11 2018 - [info] Checking replication filtering settings.. Thu May 17 21:58:11 2018 - [info] binlog_do_db= , binlog_ignore_db= Thu May 17 21:58:11 2018 - [info] Replication filtering check ok. Thu May 17 21:58:11 2018 - [info] Starting SSH connection tests.. Thu May 17 21:58:12 2018 - [info] All SSH connection tests passed successfully. Thu May 17 21:58:12 2018 - [info] Checking MHA Node version.. Thu May 17 21:58:13 2018 - [info] Version check ok. Thu May 17 21:58:13 2018 - [info] Checking SSH publickey authentication settings on the current master.. Thu May 17 21:58:13 2018 - [info] HealthCheck: SSH to 192.168.137.144 is reachable. Thu May 17 21:58:14 2018 - [info] Master MHA Node version is 0.54. Thu May 17 21:58:14 2018 - [info] Checking recovery script configurations on the current master.. Thu May 17 21:58:14 2018 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/usr/local/mysql/data/ --output_file=/masterha/save_binary_logs_test --manager_version=0.55 --start_file=mysql-bin.000002 Thu May 17 21:58:14 2018 - [info] Connecting to [email protected](192.168.137.144).. Creating /masterha if not exists.. Creating directory /masterha.. done. ok. Checking output directory is accessible or not.. ok. Binlog found at /usr/local/mysql/data/, up to mysql-bin.000002 Thu May 17 21:58:14 2018 - [info] Master setting check done. Thu May 17 21:58:14 2018 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers.. Thu May 17 21:58:14 2018 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user=‘root‘ --slave_host=192.168.137.145 --slave_ip=192.168.137.145 --slave_port=3306 --workdir=/masterha --target_version=5.7.21-log --manager_version=0.55 --relay_log_info=/usr/local/mysql/data/relay-log.info --relay_dir=/usr/local/mysql/data/ --slave_pass=xxx Thu May 17 21:58:14 2018 - [info] Connecting to [email protected](192.168.137.145:22).. Creating directory /masterha.. done. Checking slave recovery environment settings.. Opening /usr/local/mysql/data/relay-log.info ... ok. Relay log found at /usr/local/mysql/binlog, up to mysql-relay-bin.000002 Temporary relay log file is /usr/local/mysql/binlog/mysql-relay-bin.000002 Testing mysql connection and privileges..mysql: [Warning] Using a password on the command line interface can be insecure. done. Testing mysqlbinlog output.. done. Cleaning up test file(s).. done. Thu May 17 21:58:15 2018 - [info] Slaves settings check done. Thu May 17 21:58:15 2018 - [info] 192.168.137.144 (current master) +--192.168.137.145 Thu May 17 21:58:15 2018 - [info] Checking replication health on 192.168.137.145.. Thu May 17 21:58:15 2018 - [info] ok. Thu May 17 21:58:15 2018 - [warning] master_ip_failover_script is not defined. Thu May 17 21:58:15 2018 - [warning] shutdown_script is not defined. Thu May 17 21:58:15 2018 - [info] Got exit code 0 (Not master dead). MySQL Replication Health is OK.
VIP
VIP恢復master1後, 重新啟動manager後發現報錯
解決方法:按提示刪除指定文件即可。
MYSQL之MHA集群