MHA高可用配置及故障切换

MHA概述

一套优秀的MySQL高可用环境下故障切换和主从复制的软件

MySQL故障过程中，MHA能做到0-30秒内自动完成故障切换

MHA的组成

MHA Manager （管理节点）

MHA Node （数据节点）

MHA特点

自动故障切换过程中，MHA试图从宕机的主服务器上保存二进制日志，最大程度的保证数据不丢失

使用半同步复制，可以大大降低数据丢失的风险

目前MAH支持一主多从架构，最少三台服务器，即一主两从

四台机器CentOS7

两核4G

修改主机名 第一台manager 第二台master 第三台slave1 第四台slave2

 先部署MySQL数据库在上面部署主从复制（manager除外）

主从复制的代码在http://t.csdnimg.cn/6BrEf

四台机器都配置

cat >> /etc/hosts <<EOF
192.168.93.132 manager
192.168.93.133 master
192.168.93.134 slave1
192.168.93.135 slave2
EOF

在master，slave1，slave2节点安装MySQL，部署主从复制，master为主节点，slave1和slave2为从节点

在两个从节点执行
set global read_only=1;

 四台机器安装

yum install -y epel-release
yum install -y perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager \
perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker perl-CPAN
tar zxvf mha4mysql-node-0.57.tar.gz
cd mha4mysql-node-0.57
perl Makefile.PL
make
make install
tar zxvf mha4mysql-manager-0.57.tar.gz
cd mha4mysql-manager-0.57
perl Makefile.PL
make
make install

 在manager节点上面免密操作

ssh-keygen        #回车
ssh-copy-id master        #yes之后输入密码
ssh-copy-id slave1        #yes之后输入密码
ssh-copy-id slave2        #yes之后输入密码

 在master上面进行免密操作

ssh-keygen -t rsa        #回车
ssh-copy-id slave1        #yes之后输入密码
ssh-copy-id slave2        #yes之后输入密码

 在slave1上面进行免密操作

ssh-keygen -t rsa        #回车
ssh-copy-id master        #yes之后输入密码
ssh-copy-id slave2        #yes之后输入密码

在slave2上面进行免密操作

ssh-keygen -t rsa        #回车
ssh-copy-id master        #yes之后输入密码
ssh-copy-id slave1        #yes之后输入密码

在manager上面操作

cp /root/mha4mysql-manager-0.57/samples/scripts/* /usr/local/bin
vi /usr/local/bin/master_ip_failover        #把里面的配置文件替换为下面的配置文件在下面图片里里面有需要修改的东西
#!/usr/bin/env perl

#  Copyright (C) 2011 DeNA Co.,Ltd.
#  You should have received a copy of the GNU General Public License
#   along with this program; if not, write to the Free Software
#  Foundation, Inc.,
#  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA

## Note: This is a sample script and is not complete. Modify the script based on your environment.

use strict;
use warnings FATAL => 'all';

use Getopt::Long;
use MHA::DBHelper;

my (
  $command,        $ssh_user,         $orig_master_host,
  $orig_master_ip, $orig_master_port, $new_master_host,
  $new_master_ip,  $new_master_port,  $new_master_user,
  $new_master_password
);

my $vip = '192.168.93.200/24';
my $key = '1';
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip up";
my $ssh_stop_vip = "/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,
  'new_master_user=s'     => \$new_master_user,
  'new_master_password=s' => \$new_master_password,
);

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";
}

[root@manager ~]# mkdir /etc/masterha
[root@manager ~]# cp /root/mha4mysql-manager-0.57/samples/conf/app1.cnf /etc/masterha/
[root@manager ~]# 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
user=mha
password=manager
ping_interval=1
remote_workdir=/tmp
repl_user=myslave
repl_password=123456
secondary_check_script=/usr/local/bin/masterha_secondary_check -s 192.168.93.134 -s 192.168.93.135
shutdown_script=""
ssh_user=root

[server1]
hostname=192.168.93.133
port=3306

[server2]
hostname=192.168.93.134
port=3306
candidate_master=1
check_repl_delay=0

[server3]
hostname=192.168.93.135
port=3306
[root@manager ~]# mkdir -p /var/log/masterha/app1

 在master里面操作

mysql -u roor -p123
grant all privileges on *.* to 'mha'@'192.168.93.%' identified by 'manager';
GRANT REPLICATION SLAVE ON *.* TO 'myslave'@'192.168.93.%' IDENTIFIED BY '123456';
然后再创建软链接
ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/
ln -s /usr/local/mysql/bin/mysql /usr/sbin/

在两个从节点创建软链接

创建软链接
ln -s /usr/local/mysql/bin/mysqlbinlog /usr/sbin/
ln -s /usr/local/mysql/bin/mysql /usr/sbin/

在manager上面验证免密

masterha_check_ssh -conf=/etc/masterha/app1.cnf
masterha_check_repl -conf=/etc/masterha/app1.cnf

 master节点执行

ifconfig ens33:1 192.168.93.200

在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 &
tail -f /var/log/masterha/app1/manager.log

在master里执行

[root@master ~]# systemctl stop mysqld

在slave1里面执行

ifconfig

确保所有服务器的时间同步，避免主从复制出现问题

在使用MHA时，建议结合MySQL的半同步复制，以降低数据丢失的风险

在进行MHA配置时，请详细阅读官方文档和最佳实践，确保配置的正确性和安全性