MHA高可用配置及故障切换

最新推荐文章于 2021-07-10 09:39:01 发布

咕咕咕daisy！

最新推荐文章于 2021-07-10 09:39:01 发布

阅读量286

点赞数

分类专栏：笔记及项目文章标签： linux 数据库 mysql

本文链接：https://blog.csdn.net/weixin_49343462/article/details/111879503

版权

笔记及项目专栏收录该内容

59 篇文章 6 订阅

订阅专栏

MHA

MHA概述

—套优秀的MySQL高可用环境下故障切换和主从复制的软件
MySQL故障过程中，MHA能做到O-30秒内自动完成故障切换

MHA的组成

MHA Manager(管理节点)
MHA Node (数据节点)

架构图

在这里插入图片描述
组成员为数据节点

MHA特点

自动故障切换过程中，MHA试图从宕机的主服务器上保存二进制日志，最大程度的保证数据不丢失
使用半同步复制，可以大大降低数据丢失的风险
目前MHA支持一主多从架构，最少三台服务，即一主两从

在这里插入图片描述
MHA：现状node 再装manager

项目

安装MySQL5.3，并配置主从

主ip：20.0.0.10
从1：20.0.0.11
从2：20.0.0.12

在三台 MySQL 节点上分别安装数据库，MySQL 版本请使用 5.6.36，cmake 版本请使用 2.8.6。
下面只在 Mysql1 上面做演示，安装过程如下。

安装编译依赖的环境

[root@Mysql1 ~]# yum -y install ncurses-devel gcc-c++ perl-Module-Install

安装 gmake 编译软件

[root@Mysql1 ~]# tar zxvf cmake-2.8.6.tar.gz
[root@Mysql1 ~]# cd cmake-2.8.6
[root@Mysql1 cmake-2.8.6]# ./configure
[root@Mysql1 cmake-2.8.6]# gmake && gmake install

安装 MySQL 数据库

[root@Mysql1 ~]# tar -zxvf mysql-5.6.36.tar.gz
[root@Mysql1 ~]# cd mysql-5.6.36
[root@Mysql1 mysql-5.6.36]# cmake -DCMAKE_INSTALL_PREFIX=/usr/local/mysql -DDEFAULT_CHARSET=utf8 -DDEFAULT_COLLATION=utf8_general_ci -DWITH_EXTRA_CHARSETS=all -DSYSCONFDIR=/etc
[root@Mysql1 mysql-5.6.36]# make && make install
[root@Mysql1 mysql-5.6.36]# cp support-files/my-default.cnf /etc/my.cnf
[root@Mysql1 mysql-5.6.36]# cp support-files/mysql.server /etc/rc.d/init.d/mysqld
[root@Mysql1 ~]# chmod +x /etc/rc.d/init.d/mysqld
[root@Mysql1 ~]# chkconfig --add mysqld
[root@Mysql1 ~]# echo "PATH=$PATH:/usr/local/mysql/bin" >> /etc/profile
[root@Mysql1 ~]# source /etc/profile
[root@Mysql1 ~]# groupadd mysql
[root@Mysql1 ~]# useradd -M -s /sbin/nologin mysql -g mysql
[root@Mysql1 ~]# chown -R mysql.mysql /usr/local/mysql
[root@Mysql1 ~]# mkdir -p /data/mysql
[root@Mysql1 ~]# /usr/local/mysql/scripts/mysql_install_db --basedir=/usr/local/mysql --datadir=/usr/local/mysql/data --user=mysql

修改 Master 的主配置文件/etc/my.cnf 文件，三台服务器的

server-id 不能一样，另外两台写 2 和 3 即可！写入内容如下：
master:
[root@Mysql1 ~]# vi /etc/my.cnf
[client]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 1
log_bin = master-bin
log-slave-updates = true

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,PIPES_AS_CONCAT,ANSI_QUOTES

配置从服务器1：

在/etc/my.cnf 中修改或者增加下面内容。
[root@Mysql2 ~]# vi /etc/my.cnf
[client]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 2
log_bin = master-bin
relay-log = relay-log-bin 
relay-log-index = slave-relay-bin.index 

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,PIPES_AS_CONCAT,ANSI_QUOTES

配置从服务器2：

在/etc/my.cnf 中修改或者增加下面内容。
[root@Mysql2 ~]# vi /etc/my.cnf
[client]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysql]
port = 3306
socket = /usr/local/mysql/mysql.sock

[mysqld]
user = mysql
basedir = /usr/local/mysql
datadir = /usr/local/mysql/data
port = 3306
pid-file = /usr/local/mysql/mysqld.pid
socket = /usr/local/mysql/mysql.sock
server-id = 3
log_bin = master-bin
relay-log = relay-log-bin 
relay-log-index = slave-relay-bin.index 

sql_mode=NO_ENGINE_SUBSTITUTION,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_ZERO,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,PIPES_AS_CONCAT,ANSI_QUOTES

这里要注意 server-id 不能相同。

Mysql1、Mysql2、Mysql3 分别做两个软链接，软链接是为 HMA 服务的。

[root@Mysql1 ~]# ln -s /usr/local/mysql/bin/mysql /usr/sbin/
[root@Mysql1 ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/

Mysql1、Mysql2、Mysql3 启动 MySQL。

[root@Mysql1 ~]# /usr/local/mysql/bin/mysqld_safe --user=mysql &

[root@Mysql1 ~]# mysql

在这里插入图片描述

配置 MySQL 一主两从

MySQL 主从配置相对比较简单。需要注意的是授权。步骤如下：
在所有数据库节点上授权两个用户，一个是从库同步使用，另外一个是 manager 使用。

mysql> grant replication slave on *.* to 'myslave'@'20.0.0.%' identified by '123';
mysql> grant all privileges on *.* to 'mha'@'20.0.0.%' identified by 'manager';
mysql> flush privileges;

下面三条授权按理论是不用添加的，但是做案例实验环境时候通过 MHA 检查
MySQL 主从有报错，报两个从库通过主机名连接不上主库，所以所有数据库加上下面的授
权。

mysql> grant all privileges on *.* to 'mha'@'master' identified by 'manager';
mysql> grant all privileges on *.* to 'mha'@'slave1' identified by 'manager';
mysql> grant all privileges on *.* to 'mha'@'slave2' identified by 'manager';

在 Mysql1 主机上查看二进制文件和同步点。

mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 |     1416 |              |                  |                   |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

在这里插入图片描述

接下来在 Mysql2 和 Mysql3 分别执行同步。

mysql> change master to
master_host='20.0.0.10',master_user='myslave',master_password='123',master_log_file='master-bin.000001',master_log_pos=1416; //和上一章保持一致

mysql> start slave;

查看 IO 和 SQL 线程都是 yes 代表同步是否正常。

mysql> show slave status\G;
Slave_IO_Running: Yes
Slave_SQL_Running: Yes

必须设置两个从库为只读模式：

mysql> set global read_only=1;

在 Mysql1 主库插入两条数据，测试是否同步。

mysql> create database test_db;
Query OK, 1 row affected (0.00 sec)
mysql> use test_db;
Database changed
mysql> create table test(id int);
Query OK, 0 rows affected (0.13 sec)
mysql> insert into test(id) values (1);
Query OK, 1 row affected (0.03 sec)

在两个从库分别查询如下所示说明主从同步正常。

mysql> select * from test_db.test;

在这里插入图片描述

一主两从配置成功

安装 MHA 软件

所有服务器上都安装 MHA 依赖的环境，首先安装 epel 源。

[root@MHA-manager ~]# yum install epel-release --nogpgcheck
[root@MHA-manager ~]# yum install -y perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker perl-CPAN

MHA 软件包对于每个操作系统版本不一样，这里 CentOS7.3 必须选择 0.57 版本，
在所有服务器上必须先安装 node 组件，最后在 MHA-manager 节点上安装 manager 组件，
因为 manager 依赖 node 组件，下面都是在 Mysql1 上操作演示安装 node 组件。

[root@Mysql1 ~]# tar zxvf mha4mysql-node-0.57.tar.gz
[root@Mysql1 ~]# cd mha4mysql-node-0.57
[root@Mysql1 mha4mysql-node-0.57]# perl Makefile.PL
[root@server1 mha4mysql-node-0.57]# perl Makefile.PL
*** Module::AutoInstall version 1.06
*** Checking for Perl dependencies...
[Core Features]
- DBI        ...loaded. (1.627)
- DBD::mysql ...loaded. (4.023)
*** Module::AutoInstall configuration finished.
Checking if your kit is complete...
Looks good
Writing Makefile for mha4mysql::node
Writing MYMETA.yml and MYMETA.json

[root@Mysql1 mha4mysql-node-0.57]# make
[root@Mysql1 mha4mysql-node-0.57]# make install

在这里插入图片描述

在 MHA-manager 上安装 manager 组件

[root@server4 ~]# tar zxvf mha4mysql-manager-0.57.tar.gz
[root@server4 ~]# cd mha4mysql-manager-0.57/
[root@server4 mha4mysql-manager-0.57]# perl Makefile.PL 
*** Module::AutoInstall version 1.06
*** Checking for Perl dependencies...
[Core Features]
- DBI                   ...loaded. (1.627)
- DBD::mysql            ...loaded. (4.023)
- Time::HiRes           ...loaded. (1.9725)
- Config::Tiny          ...loaded. (2.14)
- Log::Dispatch         ...loaded. (2.41)
- Parallel::ForkManager ...loaded. (1.18)
- MHA::NodeConst        ...loaded. (0.57)
*** Module::AutoInstall configuration finished.
Checking if your kit is complete...
Looks good
Writing Makefile for mha4mysql::manager

[root@MHA-manager mha4MHA-manager-0.57]# make
[root@MHA-manager mha4MHA-manager-0.57]# make install

在这里插入图片描述

注：
manager 安装后在/usr/local/bin 下面会生成几个工具，主要包括以下几个：
masterha_check_ssh 检查 MHA 的 SSH 配置状况
masterha_check_repl 检查 MySQL 复制状况
masterha_manger 启动 manager的脚本
masterha_check_status 检测当前 MHA 运行状态
masterha_master_monitor 检测 master 是否宕机
masterha_master_switch 控制故障转移（自动或者手动）
masterha_conf_host 添加或删除配置的 server 信息
masterha_stop 关闭manager
在这里插入图片描述

node 安装后也会在/usr/local/bin 下面会生成几个脚本（这些工具通常由 MHA
Manager 的脚本触发，无需人为操作）主要如下：
save_binary_logs 保存和复制 master 的二进制日志
apply_diff_relay_logs 识别差异的中继日志事件并将其差异的事件应用于其他的 slave
filter_mysqlbinlog 去除不必要的 ROLLBACK 事件（MHA 已不再使用这个工具）
purge_relay_logs 清除中继日志（不会阻塞 SQL 线程）

配置无密码认证

在 manager 上配置到所有节点的无密码认证

[root@server4 ~]# ssh-keygen -t rsa //一路按回车键
[root@server4 ~]# ssh-copy-id 20.0.0.10
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '20.0.0.10 (20.0.0.10)' can't be established.
ECDSA key fingerprint is SHA256:qnRMEbaGaFHrck/x4p8GO9RJD5vgaTgPObOpT3uU9nM.
ECDSA key fingerprint is MD5:30:b2:7d:15:15:8b:1a:65:27:78:55:6a:39:0a:7c:af.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@20.0.0.10's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh '20.0.0.10'"
and check to make sure that only the key(s) you wanted were added.

[root@server4 ~]# ssh 20.0.0.10
Last login: Tue Dec 29 13:43:47 2020 from 20.0.0.1
[root@server1 ~]# exit
登出
Connection to 20.0.0.10 closed.
[root@server4 ~]# ssh-copy-id 20.0.0.11  //按上述继续配置
[root@server4 ~]# ssh-copy-id 20.0.0.12

在这里插入图片描述

在 Mysql1 上配置到数据库节点的无密码认证

[root@server1 ~]# ssh-keygen -t rsa
[root@server1 ~]# ssh-copy-id 20.0.0.11
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '20.0.0.11 (20.0.0.11)' can't be established.
ECDSA key fingerprint is SHA256:kMJc6r0eXxa/3K7BTIY3Qx/1iIm3JjNxZSPZjEpfJGE.
ECDSA key fingerprint is MD5:fd:2a:2e:5d:cd:e1:0d:2b:39:fa:f9:11:b9:4d:34:09.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@20.0.0.11's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh '20.0.0.11'"
and check to make sure that only the key(s) you wanted were added.


[root@server1 ~]# ssh-copy-id 20.0.0.12  //按上述继续配置

在这里插入图片描述

在 Mysql2 上配置到数据库节点的无密码认证

[root@server2 ~]# ssh-keygen -t rsa
[root@server2 ~]# ssh-copy-id 20.0.0.10
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
The authenticity of host '20.0.0.10 (20.0.0.10)' can't be established.
ECDSA key fingerprint is SHA256:qnRMEbaGaFHrck/x4p8GO9RJD5vgaTgPObOpT3uU9nM.
ECDSA key fingerprint is MD5:30:b2:7d:15:15:8b:1a:65:27:78:55:6a:39:0a:7c:af.
Are you sure you want to continue connecting (yes/no)? yes
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@20.0.0.10's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh '20.0.0.10'"
and check to make sure that only the key(s) you wanted were added.

[root@server2 ~]# ssh-copy-id 20.0.0.12    //按上述继续配置

在这里插入图片描述

在 Mysql3 上配置到数据库节点的无密码认证

[root@server3 ~]# ssh-keygen -t rsa
[root@server3 ~]# ssh-copy-id 20.0.0.10
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@20.0.0.10's password: 

Number of key(s) added: 1

Now try logging into the machine, with:   "ssh '20.0.0.10'"
and check to make sure that only the key(s) you wanted were added.

[root@server3 ~]# ssh-copy-id 20.0.0.11    //按上述继续配置

在这里插入图片描述

配置 MHA

在 manager 节点上复制相关脚本到/usr/local/bin 目录。

[root@server4 ~]# cp -ra /root/mha4mysql-manager-0.57/samples/scripts /usr/local/bin
//拷贝后会有四个执行文件
[root@server4 ~]# ll /usr/local/bin/scripts/
总用量 32
-rwxr-xr-x. 1 1001 1001  3648 5月  31 2015 master_ip_failover
-rwxr-xr-x. 1 1001 1001  9870 5月  31 2015 master_ip_online_change
-rwxr-xr-x. 1 1001 1001 11867 5月  31 2015 power_manager
-rwxr-xr-x. 1 1001 1001  1360 5月  31 2015 send_report

在这里插入图片描述
附：

master_ip_failover ：自动切换时 VIP 管理的脚本
master_ip_online_change ：在线切换时 vip 的管理
power_manager ：故障发生后关闭主机的脚本
send_report ：因故障切换后发送报警的脚本

复制上述的自动切换时 VIP 管理的脚本到/usr/local/bin 目录，这里使用脚本管理 VIP，也是推荐的一种方式，生产环境不太建议使用 keepalived。

[root@server4 ~]# cp /usr/local/bin/scripts/master_ip_failover /usr/local/bin

替换脚本

[root@server4 ~]# vi /usr/local/bin/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 = '20.0.0.200';
my $brdc = '20.0.0.255';
my $ifdev = 'ens33';
my $key = '1';
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down";
my $exit_code = 0;
#my $ssh_start_vip = "/usr/sbin/ip addr add $vip/24 brd $brdc dev $ifdev label $ifdev:$key;/usr/sbin/arping -q -A -c 1 -I $ifdev $vip;iptables -F;";
#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" ) {

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 \"`;
}
# 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";
}

[root@server4 ~]# mkdir /etc/masterha
[root@server4 ~]# cp /root/mha4mysql-manager-0.57/samples/conf/app1.cnf /etc/masterha
[root@server4 ~]# vi /etc/masterha/app1.cnf   //替换内容如下

[server default]
manager_workdir=/var/log/masterha/app1
manager_log=/var/log/masterha/app1/manager.log
master_binlog_dir=/usr/local/mysql/data
master_ip_failover_script= /usr/local/bin/master_ip_failover
master_ip_online_change_script= /usr/local/bin/master_ip_online_change
password=manager
user=mha
ping_interval=1
remote_workdir=/tmp
repl_password=123
repl_user=myslave
secondary_check_script= /usr/local/bin/masterha_secondary_check -s 20.0.0.11 -s 20.0.0.12
shutdown_script="" 
ssh_user=root
[server1]
hostname=20.0.0.10
port=3306
[server2]
hostname=20.0.0.11
port=3306
candidate_master=1
check_repl_delay=0
[server3]
hostname=20.0.0.12
port=3306

测试 ssh 无密码认证，如果正常最后会输出 successfully

[root@server4 ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf

在这里插入图片描述

测试 MySQL 主从连接情况
最后出现 MySQL Replication Health is OK 字样说明
正常

[root@manager ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf

在这里插入图片描述

查看 Mysql1 的 VIP 地址 20.0.0.200 是否存在
这个 VIP 地址不会因为manager 节点停止 MHA 服务而消失

[root@master ~]# ifconfig ens33:1 20.0.0.200/24
[root@master ~]# ifconfig 
ens33:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 20.0.0.200  netmask 255.255.255.0  broadcast 20.0.0.255
        ether 00:0c:29:ee:4c:3d  txqueuelen 1000  (Ethernet)

在这里插入图片描述

查看 MHA 状态
看到当前的 master 是 Mysql1 节点

[root@manager ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:56348) is running(0:PING_OK), master:20.0.0.10

在这里插入图片描述

查看 MHA 日志
看到当前的 master 是 20.0.0.10

[root@manager ~]# cat /var/log/masterha/app1/manager.log

在这里插入图片描述

启动 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] 56348

注：

–remove_dead_master_conf 该参数代表当发生主从切换后，老的主库的 ip 将会从配置文件中移除。
–manger_log 日志存放位置。
–ignore_last_failover 在缺省情况下，如果 MHA 检测到连续发生宕机，且两次宕机间隔不足 8 小时的话，则不会进行 Failover，之所以这样限制是为了避免 ping-pong 效应。该参数代表忽略上次 MHA 触发切换产生的文件，默认情况下，MHA 发生切换后会在日志记目录，也就是上面设置的日志 app1.failover.complete 文件，下次再次切换的时候如果发现该目录下存在该文件将不允许触发切换，除非在第一次切换后收到删除该文件，为了方便，这里设置为–ignore_last_failover。

故障模拟

在主库上

[root@master ~]# pkill mysql

可以看到从库的状态，其中之一肯定有切换到主库的
在从服务器slave1上查看

mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 |     1802 |              |                  |                   |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

再到slave2上查看

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 20.0.0.11
                  Master_User: myslave
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: master-bin.000001
          Read_Master_Log_Pos: 1802
               Relay_Log_File: relay-log-bin.000002
                Relay_Log_Pos: 284
        Relay_Master_Log_File: master-bin.000001
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes

在这里插入图片描述
故障成功

故障修复

修复db

[root@master ~]# /etc/init.d/mysqld start
Starting MySQL. SUCCESS!

在这里插入图片描述

修复主从
现master（原slave1）上查看

mysql> show master status;
+-------------------+----------+--------------+------------------+-------------------+
| File              | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-------------------+----------+--------------+------------------+-------------------+
| master-bin.000001 |     1802 |              |                  |                   |
+-------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

在这里插入图片描述

原master

mysql> change master to
    -> master_host='20.0.0.11',master_user='myslave',master_password='123',master_log_file='master-bin.000001',master_log_pos=1802; 
Query OK, 0 rows affected, 2 warnings (0.01 sec)

mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

在这里插入图片描述

修改配置文件（在manager那台机器上）

[root@manager ~]# vi /etc/masterha/app1.cnf
[server1]  //此数据可能会消失，手动添加
hostname=20.0.0.10
port=3306

[server2]
hostname=20.0.0.11
port=3306
candidate_master=1   //删除
check_repl_delay=0   //删除

启动manager（在manager那台机器上）

[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] 61094

在这里插入图片描述

查看新master（原slave1）的vip地址漂移

[root@slave1 ~]# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:be:f9:9a brd ff:ff:ff:ff:ff:ff
    inet 20.0.0.11/24 brd 20.0.0.255 scope global ens33
       valid_lft forever preferred_lft forever
    inet 20.0.0.200/8 brd 20.255.255.255 scope global ens33:1
       valid_lft forever preferred_lft forever
    inet6 fe80::5fbd:7a94:cd19:521f/64 scope link 
       valid_lft forever preferred_lft forever
3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000
    link/ether 52:54:00:07:18:7f brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN qlen 1000
    link/ether 52:54:00:07:18:7f brd ff:ff:ff:ff:ff:ff

在这里插入图片描述
vip地址漂移成功

在manager那台机器上

[root@manager ~]# masterha_stop --conf=/etc/masterha/app1.cnf
Stopped app1 successfully.
[1]+  退出 1                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
[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] 61270

在这里插入图片描述

再次检查ssh和健康状态

[root@manager ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf
Wed Dec 30 12:05:52 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Wed Dec 30 12:05:52 2020 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Wed Dec 30 12:05:52 2020 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Wed Dec 30 12:05:52 2020 - [info] Starting SSH connection tests..
Wed Dec 30 12:05:52 2020 - [debug] 
Wed Dec 30 12:05:52 2020 - [debug]  Connecting via SSH from root@20.0.0.11(20.0.0.11:22) to root@20.0.0.12(20.0.0.12:22)..
Wed Dec 30 12:05:52 2020 - [debug]   ok.
Wed Dec 30 12:05:53 2020 - [debug] 
Wed Dec 30 12:05:52 2020 - [debug]  Connecting via SSH from root@20.0.0.12(20.0.0.12:22) to root@20.0.0.11(20.0.0.11:22)..
Wed Dec 30 12:05:53 2020 - [debug]   ok.
Wed Dec 30 12:05:53 2020 - [info] All SSH connection tests passed successfully.

在这里插入图片描述

[root@manager ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf

在这里插入图片描述
修复成功

咕咕咕daisy！

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫

专栏目录