MHA高可用配置和故障切换
为什么要用MHA
传统的MySQL主从架构存在如果存在问题，比如主服务器出现故障后就无法写入数据了，那么MHA是一套优秀的MySQL高可用环境下故障切换和主从复制的软件，当MySQL故障过程中，MHA能做到0-30秒内自动完成故障切换。
MHA
MHA组成MHA Manager（管理节点）和MHA Node（数据节点），MHA Manger管理多个集群（master-slave），Manger是单独一台监控master服务器健康状态的服务器也可以部署在一台slave上面，MHA Node运行在每台MySQL服务器上，MHA Manger会定时探测集群中的master节点，当master出现了故障，MHA Manger会自动将最新数据的slave提升为master，然后将所有其他的slave重新指向新的master。
MHA优势
MHA自动故障切换过程中，MHA从挂掉的主服务器上保存二进制文件，最大程度的保证了数据的不丢失，但是如果主服务器硬件出现了故障或者无法通过ssh访问，MHA就无法保存二进制文件，只能进行故障转移但是丢失了最新的数据。使用MySQL5.5的半同步复制，可以大大的降低数据丢失的风险，MHA可以与半同步复制结合，如果只有一个slave收到最新的二进制文件,MHA可以将最新的二进制日志应用于其他所有slave服务器上，因此可以保证所有节点的一致性，这里可以设置从节点慢于主节点，当发生事故删除数据库可以从节点二进制日志中恢复。
实现MHA高可用环境
- master
[root@master ~]# vim /etc/my.cnf //在目标位置插入三条内容
[mysqld]
server-id = 1
log_bin = master-bin //开启二进制日志文件
log-slave-updates = true //允许从服务器同步
[root@master ~]# ln -s /usr/local/mysql/bin/mysql /usr/sbin/
[root@master ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/
- slave1
[root@slave1 ~]# vim /etc/my.cnf **开启中继日志，创建索引，同步主服务器
[mysqld]
server-id = 2
log_bin=master-bin
relay-log=relay-log-bin
relay-log-index=slave-realy-bin.index
[root@master ~]# ln -s /usr/local/mysql/bin/mysql /usr/sbin/
[root@master ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/
- slave2
[root@slave2 ~]# vim /etc/my.cnf
[mysqld]
server-id = 3
log_bin=master-bin
relay-log=relay-log-bin
relay-log-index=slave-relay-bin.index
[root@master ~]# ln -s /usr/local/mysql/bin/mysql /usr/sbin/
[root@master ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/
- all
grant replication slave on *.* to 'myslave'@'192.168.20.%' identified by '123456';
grant all privileges on *.* to 'mha'@'192.168.20.%' identified by 'manager';
grant all privileges on *.* to 'mha'@'master' identified by 'manager';
grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';
主从复制
- master
mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 | 154 | | | |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
- slave1
mysql> change master to master_host='192.168.20.11',master_user='myslave',master_password='123456',master_log_file='master-bin.000001',master_log_pos=154;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
mysql> start slave;
Query OK, 0 rows affected (0.01 sec)
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.20.11
Master_User: myslave
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master-bin.000001
Read_Master_Log_Pos: 154
Relay_Log_File: localhost-relay-bin.000002
Relay_Log_Pos: 321
Relay_Master_Log_File: master-bin.000001
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
- slave2
mysql> change master to master_host='192.168.20.11',master_user='myslave',master_password='123456',master_log_file='master-bin.000001',master_log_pos=154;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
mysql> start slave;
Query OK, 0 rows affected (0.01 sec)
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.20.11
Master_User: myslave
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master-bin.000001
Read_Master_Log_Pos: 154
Relay_Log_File: localhost-relay-bin.000002
Relay_Log_Pos: 321
Relay_Master_Log_File: master-bin.000001
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
安装和配置MHA
- all
[root@localhost ~]# yum install epel-release --nogpgcheck -y //安装epel源，
[root@localhost ~]# yum install -y perl-DBD-MySQL \
> perl-Config-Tiny \
> perl-Log-Dispatch \ //log日志
> perl-Parallel-ForkManager \
> perl-ExtUtils-CBuilder \
> perl-ExtUtils-MakeMaker \ //扩展工具
> perl-CPAN //cpan perl中的数据库
[root@localhost ~]# crontab -l //定时任务每十分钟同步阿里云时间服务器
*/10 * * * * /usr/sbin/ntpdate ntp.aliyun.com
- node组件
[root@localhost opt]# tar zxvf /opt/mha4mysql-node-0.57.tar.gz
[root@localhost opt]# cd mha4mysql-node-0.57/
[root@localhost mha4mysql-node-0.57]# perl Makefile.PL
[root@localhost mha4mysql-node-0.57]# make && make install
- manager
[root@localhost mha4mysql-node-0.57]# tar zxvf /opt/mha4mysql-manager-0.57.tar.gz
[root@localhost mha4mysql-node-0.57]# cd mha4mysql-manager-0.57
[root@localhost mha4mysql-manager-0.57]# perl Makefile.PL
[root@localhost mha4mysql-manager-0.57]# make && make install
- node和manager安装后生成的几个工具
[root@localhost bin]# ll
总用量 84
-r-xr-xr-x. 1 root root 16381 7月 24 17:27 apply_diff_relay_logs //识别差异的中继日志时间，并将其差异的时间应用于其他的slave
-r-xr-xr-x. 1 root root 4807 7月 24 17:27 filter_mysqlbinlog //去除不必要的回滚时间
-r-xr-xr-x. 1 root root 1995 7月 24 17:28 masterha_check_repl //检查MYSQL复制状况
-r-xr-xr-x. 1 root root 1779 7月 24 17:28 masterha_check_ssh //检查MHA的ssh配置状况
-r-xr-xr-x. 1 root root 1865 7月 24 17:28 masterha_check_status //检查manager
的脚本
-r-xr-xr-x. 1 root root 3201 7月 24 17:28 masterha_conf_host //添加或删除配置的server信息
-r-xr-xr-x. 1 root root 2517 7月 24 17:28 masterha_manager //启动manager的脚本
-r-xr-xr-x. 1 root root 2165 7月 24 17:28 masterha_master_monitor //检查master是否宕机
-r-xr-xr-x. 1 root root 2373 7月 24 17:28 masterha_master_switch //空值故障转移（自动或手动）
-r-xr-xr-x. 1 root root 5171 7月 24 17:28 masterha_secondary_check
-r-xr-xr-x. 1 root root 1739 7月 24 17:28 masterha_stop //关闭manager
-r-xr-xr-x. 1 root root 8261 7月 24 17:27 purge_relay_logs //清除中继日志
-r-xr-xr-x. 1 root root 7525 7月 24 17:27 save_binary_logs //保存和复制master的二进制日志
[root@localhost bin]# pwd
/usr/local/bin
- 配置无密码认证
- all
[root@localhost ~]# ssh-keygen -t rsa
ssh-copy-id 192.168.20.11
ssh-copy-id 192.168.20.22
ssh-copy-id 192.168.20.33
ssh-copy-id 192.168.20.44
- 配置MHA
[root@manager ~]# cp -ra /opt/mha4mysql-node-0.57/mha4mysql-manager-0.57/samples/scripts/ /usr/local/bin/ //在MHA上复制相关的脚本到目录
[root@manager ~]# ll /usr/local/bin/scripts/
总用量 32
-rwxr-xr-x. 1 mysql mysql 3648 5月 31 2015 master_ip_failover //自动切换时VIP管理的脚本
-rwxr-xr-x. 1 mysql mysql 9870 5月 31 2015 master_ip_online_change //在线切换时VIP的管理
-rwxr-xr-x. 1 mysql mysql 11867 5月 31 2015 power_manager //故障发生后关闭主机的脚本
-rwxr-xr-x. 1 mysql mysql 1360 5月 31 2015 send_report //因故障切换后发送报警
[root@manager ~]# vim /usr/local/bin/scripts/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.20.100'; //浮动ip
my $brdc = '192.168.20.255'; //广播地址
my $ifdev = 'ens33'; //使用二的网卡为ens33
my $key = '1'; //国际序列号
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip"; //使用ifconfig命令将其启动，同时设置浮动地址
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down"; //使用ifconfig命令将其down掉
my $exit_code = 0; //正常退出（返回状态码）
#my $ssh_stop_vip = "/usr/sbin/ip addr del $vip/24 dev $ifdev label $ifdev:$key";
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" ) {
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 \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
`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";
}
- 创建MHA软件目录并拷贝配置文件
[root@manager ~]# mkdir /etc/masterha
[root@manager ~]# cp /opt/mha4mysql-node-0.57/mha4mysql-manager-0.57/samples/conf/app1.cnf /etc/masterha/
[root@manager ~]# vim /etc/masterha/app1.cnf
您在 /var/spool/mail/root 中有新邮件
[root@manager ~]# vim /etc/masterha/app1.cnf
#工作目录
manager_workdir=/var/log/masterha/app1
#二进制文件
master_binlog_dir=/usr/local/mysql/data
#故障转移切换的工具
master_ip_failover_script=/usr/local/bin/master_ip_failover
#在线切换VIP工具管理
master_ip_online_change_script=/usr/local/bin/master_ip_online_change
#以下是密码账号的管理配置
password=manager
ping_interval=1
remote_workdir=/tmp
repl_password=123456
repl_user=myslave
secondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.20.22 -s 192.168.20.33
shutdown_script=""
ssh_user=root
user=mha
[server1]
hostname=192.168.20.11
port=3306
[server2]
candidate_master=1
hostname=192.168.20.22
check_repl_delay=0
port=3306
[server3]
hostname=192.168.20.33
- 在master节点上手动开启虚拟IP
[root@localhost data]# /sbin/ifconfig ens33:1 192.168.20.100
- 测试无密码认证，正常的话输出successfully
[root@manager ~]# masterha_check_ssh -conf=/etc/masterha/app1.cnf //测试无密码认证，正常的话输出successfully
Sat Jul 24 22:27:54 2021 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Jul 24 22:27:54 2021 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Jul 24 22:27:54 2021 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Jul 24 22:27:54 2021 - [info] Starting SSH connection tests..
Sat Jul 24 22:27:56 2021 - [debug]
Sat Jul 24 22:27:54 2021 - [debug] Connecting via SSH from root@192.168.20.11(192.168.20.11:22) to root@192.168.20.22(192.168.20.22:22)..
Sat Jul 24 22:27:55 2021 - [debug] ok.
Sat Jul 24 22:27:55 2021 - [debug] Connecting via SSH from root@192.168.20.11(192.168.20.11:22) to root@192.168.20.33(192.168.20.33:22)..
Sat Jul 24 22:27:55 2021 - [debug] ok.
Sat Jul 24 22:27:56 2021 - [debug]
Sat Jul 24 22:27:55 2021 - [debug] Connecting via SSH from root@192.168.20.22(192.168.20.22:22) to root@192.168.20.11(192.168.20.11:22)..
Sat Jul 24 22:27:55 2021 - [debug] ok.
Sat Jul 24 22:27:55 2021 - [debug] Connecting via SSH from root@192.168.20.22(192.168.20.22:22) to root@192.168.20.33(192.168.20.33:22)..
Sat Jul 24 22:27:56 2021 - [debug] ok.
Sat Jul 24 22:27:57 2021 - [debug]
Sat Jul 24 22:27:55 2021 - [debug] Connecting via SSH from root@192.168.20.33(192.168.20.33:22) to root@192.168.20.11(192.168.20.11:22)..
Sat Jul 24 22:27:56 2021 - [debug] ok.
Sat Jul 24 22:27:56 2021 - [debug] Connecting via SSH from root@192.168.20.33(192.168.20.33:22) to root@192.168.20.22(192.168.20.22:22)..
Sat Jul 24 22:27:56 2021 - [debug] ok.
Sat Jul 24 22:27:57 2021 - [info] All SSH connection tests passed successfully.
- 测试主从复制
[root@manager ~]# masterha_check_repl -conf=/etc/masterha/app1.cnf
Sat Jul 24 23:08:06 2021 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Jul 24 23:08:06 2021 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Jul 24 23:08:06 2021 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Jul 24 23:08:06 2021 - [info] MHA::MasterMonitor version 0.57.
Sat Jul 24 23:08:07 2021 - [info] GTID failover mode = 0
Sat Jul 24 23:08:07 2021 - [info] Dead Servers:
Sat Jul 24 23:08:07 2021 - [info] Alive Servers:
Sat Jul 24 23:08:07 2021 - [info] 192.168.20.11(192.168.20.11:3306)
Sat Jul 24 23:08:07 2021 - [info] 192.168.20.33(192.168.20.33:3306)
Sat Jul 24 23:08:07 2021 - [info] 192.168.20.22(192.168.20.22:3306)
Sat Jul 24 23:08:07 2021 - [info] Alive Slaves:
Sat Jul 24 23:08:07 2021 - [info] 192.168.20.33(192.168.20.33:3306) Version=5.7.20-log (oldest major version between slaves) log-bin:enabled
Sat Jul 24 23:08:07 2021 - [info] Replicating from 192.168.20.11(192.168.20.11:3306)
Sat Jul 24 23:08:07 2021 - [info] Primary candidate for the new Master (candidate_master is set)
Sat Jul 24 23:08:07 2021 - [info] 192.168.20.22(192.168.20.22:3306) Version=5.7.20-log (oldest major version between slaves) log-bin:enabled
Sat Jul 24 23:08:07 2021 - [info] Replicating from 192.168.20.11(192.168.20.11:3306)
Sat Jul 24 23:08:07 2021 - [info] Current Alive Master: 192.168.20.11(192.168.20.11:3306)
Sat Jul 24 23:08:07 2021 - [info] Checking slave configurations..
Sat Jul 24 23:08:07 2021 - [info] read_only=1 is not set on slave 192.168.20.33(192.168.20.33:3306).
Sat Jul 24 23:08:07 2021 - [warning] relay_log_purge=0 is not set on slave 192.168.20.33(192.168.20.33:3306).
Sat Jul 24 23:08:07 2021 - [info] read_only=1 is not set on slave 192.168.20.22(192.168.20.22:3306).
Sat Jul 24 23:08:07 2021 - [warning] relay_log_purge=0 is not set on slave 192.168.20.22(192.168.20.22:3306).
Sat Jul 24 23:08:07 2021 - [info] Checking replication filtering settings..
Sat Jul 24 23:08:07 2021 - [info] binlog_do_db= , binlog_ignore_db=
Sat Jul 24 23:08:07 2021 - [info] Replication filtering check ok.
Sat Jul 24 23:08:07 2021 - [info] GTID (with auto-pos) is not supported
Sat Jul 24 23:08:07 2021 - [info] Starting SSH connection tests..
Sat Jul 24 23:08:09 2021 - [info] All SSH connection tests passed successfully.
Sat Jul 24 23:08:09 2021 - [info] Checking MHA Node version..
Sat Jul 24 23:08:10 2021 - [info] Version check ok.
Sat Jul 24 23:08:10 2021 - [info] Checking SSH publickey authentication settings on the current master..
Sat Jul 24 23:08:10 2021 - [info] HealthCheck: SSH to 192.168.20.11 is reachable.
Sat Jul 24 23:08:10 2021 - [info] Master MHA Node version is 0.57.
Sat Jul 24 23:08:10 2021 - [info] Checking recovery script configurations on 192.168.20.11(192.168.20.11:3306)..
Sat Jul 24 23:08:10 2021 - [info] Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/usr/local/mysql/data --output_file=/tmp/save_binary_logs_test --manager_version=0.57 --start_file=master-bin.000001
Sat Jul 24 23:08:10 2021 - [info] Connecting to root@192.168.20.11(192.168.20.11:22)..
Creating /tmp if not exists.. ok.
Checking output directory is accessible or not..
ok.
Binlog found at /usr/local/mysql/data, up to master-bin.000001
Sat Jul 24 23:08:11 2021 - [info] Binlog setting check done.
Sat Jul 24 23:08:11 2021 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Sat Jul 24 23:08:11 2021 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.20.33 --slave_ip=192.168.20.33 --slave_port=3306 --workdir=/tmp --target_version=5.7.20-log --manager_version=0.57 --relay_log_info=/usr/local/mysql/data/relay-log.info --relay_dir=/usr/local/mysql/data/ --slave_pass=xxx
Sat Jul 24 23:08:11 2021 - [info] Connecting to root@192.168.20.33(192.168.20.33:22)..
Checking slave recovery environment settings..
Opening /usr/local/mysql/data/relay-log.info ... ok.
Relay log found at /usr/local/mysql/data, up to relay-log-bin.000002
Temporary relay log file is /usr/local/mysql/data/relay-log-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.
Sat Jul 24 23:08:11 2021 - [info] Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.20.22 --slave_ip=192.168.20.22 --slave_port=3306 --workdir=/tmp --target_version=5.7.20-log --manager_version=0.57 --relay_log_info=/usr/local/mysql/data/relay-log.info --relay_dir=/usr/local/mysql/data/ --slave_pass=xxx
Sat Jul 24 23:08:11 2021 - [info] Connecting to root@192.168.20.22(192.168.20.22:22)..
Checking slave recovery environment settings..
Opening /usr/local/mysql/data/relay-log.info ... ok.
Relay log found at /usr/local/mysql/data, up to relay-log-bin.000002
Temporary relay log file is /usr/local/mysql/data/relay-log-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.
Sat Jul 24 23:08:11 2021 - [info] Slaves settings check done.
Sat Jul 24 23:08:11 2021 - [info]
192.168.20.11(192.168.20.11:3306) (current master)
+--192.168.20.33(192.168.20.33:3306)
+--192.168.20.22(192.168.20.22:3306)
Sat Jul 24 23:08:11 2021 - [info] Checking replication health on 192.168.20.33..
Sat Jul 24 23:08:11 2021 - [info] ok.
Sat Jul 24 23:08:11 2021 - [info] Checking replication health on 192.168.20.22..
Sat Jul 24 23:08:11 2021 - [info] ok.
Sat Jul 24 23:08:11 2021 - [info] Checking master_ip_failover_script status:
Sat Jul 24 23:08:11 2021 - [info] /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.20.11 --orig_master_ip=192.168.20.11 --orig_master_port=3306
IN SCRIPT TEST====/sbin/ifconfig ens33:1 down==/sbin/ifconfig ens33:1 192.168.20.100===
Checking the Status of the script.. OK
Sat Jul 24 23:08:11 2021 - [info] OK.
Sat Jul 24 23:08:11 2021 - [warning] shutdown_script is not defined.
Sat Jul 24 23:08:11 2021 - [info] Got exit code 0 (Not master dead).
MySQL Replication Health is OK.
- 启动MHA
[root@manager ~]# nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/masterha/app1/manager.log 2>&1 &
[1] 101305
- 查询当前的master节点是谁
[root@manager ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:101305) is running(0:PING_OK), master:192.168.20.11
那么把master的数据库down掉之后
[root@localhost ~]# systemctl stop mysqld.service
[root@localhost ~]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.11 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::a127:8d6a:5ef8:bcc6 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:7e:9c:75 txqueuelen 1000 (Ethernet)
RX packets 928812 bytes 1304006305 (1.2 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 373825 bytes 29614776 (28.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
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 980 bytes 127572 (124.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 980 bytes 127572 (124.5 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:6b:93:3d 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
浮动路由跳到192.168.20.33上
[root@localhost data]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.33 netmask 255.255.255.0 broadcast 192.168.20.255
inet6 fe80::66b5:d0e6:7784:dff6 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:48:82:b2 txqueuelen 1000 (Ethernet)
RX packets 594057 bytes 849117694 (809.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 114038 bytes 13776742 (13.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ens33:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.20.100 netmask 255.255.255.0 broadcast 192.168.20.255
ether 00:0c:29:48:82:b2 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 26811 bytes 2282918 (2.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 26811 bytes 2282918 (2.1 MiB)
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:23:14:e7 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
- 在manager上查看日志
[root@manager ~]# cat /var/log/masterha/app1/manager.log
................................................此处省略n日志信息
----- Failover Report -----
app1: MySQL Master failover 192.168.20.11(192.168.20.11:3306) to 192.168.20.33(192.168.20.33:3306) succeeded
Master 192.168.20.11(192.168.20.11: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.20.11(192.168.20.11:3306)
The latest slave 192.168.20.33(192.168.20.33:3306) has all relay logs for recovery.
Selected 192.168.20.33(192.168.20.33:3306) as a new master.
192.168.20.33(192.168.20.33:3306): OK: Applying all logs succeeded.
192.168.20.33(192.168.20.33:3306): OK: Activated master IP address.
192.168.20.22(192.168.20.22:3306): This host has the latest relay log events.
Generating relay diff files from the latest slave succeeded.
192.168.20.22(192.168.20.22:3306): OK: Applying all logs succeeded. Slave started, replicating from 192.168.20.33(192.168.20.33:3306)
192.168.20.33(192.168.20.33:3306): Resetting slave info succeeded.
Master failover to 192.168.20.33(192.168.20.33:3306) completed successfully.
- slave2上位成功
mysql> show slave status\G;
Empty set (0.00 sec)
ERROR:
No query specified
mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 | 867 | | | |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)
- 那么接下来在slave2创建数据
mysql> create database oo;
Query OK, 1 row affected (0.00 sec)
mysql> use oo;
Database changed
mysql> create table oo (id int);
Query OK, 0 rows affected (0.00 sec)
mysql> insert into oo value(1);
Query OK, 1 row affected (0.00 sec)
在slave1上查看
mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| hh |
| mysql |
| oo |
| performance_schema |
| sys |
+--------------------+
6 rows in set (0.00 sec)
mysql> use oo;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> show tables;
+--------------+
| Tables_in_oo |
+--------------+
| oo |
+--------------+
1 row in set (0.00 sec)
mysql> select * from oo;
+------+
| id |
+------+
| 1 |
+------+
1 row in set (0.00 sec)
465
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
