天天看点

mysql mha部署_MySQL高可用MHA环境部署

mysql mha部署_MySQL高可用MHA环境部署

配置SSH 密钥对验证:

Server05(192.168.96.9)上每台机器都发,在主从服务器的密钥对只在服务器之间发

ssh-keygen -t rsa

mysql mha部署_MySQL高可用MHA环境部署

【(双向的,每台机器互相发)】

ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected]

ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected]

ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected]

ssh-copy-id -i /root/.ssh/id_rsa.pub [email protected]

mysql mha部署_MySQL高可用MHA环境部署

ssh server01(exit退出)

ssh server02

ssh server03

ssh server04

注意:Server05 需要连接每个主机测试,因为第一次连接的时候需要输入 yes,影响后期故

障切换时,对于每个主机的 SSH 控制。(其余机器不用操作)

mysql mha部署_MySQL高可用MHA环境部署

安装MYSQL

yum -y install mariadb mariadb-server mariadb-devel

systemctl start mariadb

netstat -lnpt | grep :3306

设置数据库初始密码(密码在后面会使用)

mysqladmin -u root password 000000

搭建主从复制环境

修改mysql主机的配置文件:

primary Master(192.168.96.4):

vim /etc/my.cnf

server-id = 1

log-bin=master-bin

log-slave-updates=true

relay_log_purge=0

mysql mha部署_MySQL高可用MHA环境部署

systemctl restart mariadb

Secondary Master(192.168.96.5)

vim /etc/my.cnf

server-id=2

log-bin=master-bin

log-slave-updates=true

relay_log_purge=0

mysql mha部署_MySQL高可用MHA环境部署

systemctl restart mariadb

slave1(192.168.96.6):

vim /etc/my.cnf

server-id=3

log-bin=mysql-bin

relay-log=slave-relay-bin

log-slave-updates=true

relay_log_purge=0

mysql mha部署_MySQL高可用MHA环境部署

systemctl restart mariadb

slave2(192.168.96.7):

vim /etc/my.cnf

server-id=4

log-bin=mysql-bin

relay-log=slave-relay-bin

log-slave-updates=true

relay_log_purge=0

mysql mha部署_MySQL高可用MHA环境部署

systemctl restart mariadb

mysql服务器创建复制授权用户:(server01——04机器,登录mysql操作)

grant replication slave on *.* to 'repl'@'192.168.96.%' identified by '000000';

flush privileges;

show master status;    //查看主库备份时binlog名称和位置

mysql mha部署_MySQL高可用MHA环境部署

在从服务器操作:(每台从服务器都操作)

stop slave;

CHANGE MASTER TO

MASTER_HOST='192.168.96.4',

MASTER_USER='repl',

MASTER_PASSWORD='000000',

MASTER_LOG_FILE='master-bin.000001',

MASTER_LOG_POS=473;

start slave;

show slave status\G;

mysql mha部署_MySQL高可用MHA环境部署

三台slave服务器设置read_only状态:

从库对外只提供读服务,只所以没有写进 mysql 配置文件,是因为随时 server02 会提升为

master

[roo[email protected] ~]# mysql -uroot -p000000 -e 'set global read_only=1'

[roo[email protected] ~]# mysql -uroot -p000000 -e 'set global read_only=1'

[ro[email protected] ~]# mysql -uroot -p000000-e 'set global read_only=1'

创建监控用户(server01——04机器操作)

grant all privileges on *.* to 'root'@'192.168.200.%' identified by '123456';

flush privileges;

每一台机器为自己的主机名授权:

grant all privileges on *.* to 'root'@'server04' identified by '000000';

flush privileges;

配置MHA环境:

Server05(192.168.96.9):在软件包解压后的目录里面有样例配置文件

mkdir /etc/masterha

cp mha4mysql-manager-0.56/samples/conf/app1.cnf /etc/masterha

vim /etc/masterha/app1.cnf      //修改配置文件

【添加内容】

#设置 master 默认保存 binlog 的位置,以便 MHA 可以找到 master 日志

master_binlog_dir=/var/lib/mysql

#设置自动 failover 时候的切换脚本

master_ip_failover_script= /usr/local/bin/master_ip_failover

#设置 mysql 中 root 用户的密码

password=000000

user=root

#ping 包的时间间隔

ping_interval=1

#设置远端 mysql 在发生切换时保存 binlog 的具体位置

remote_workdir=/tmp

#设置复制用户的密码和用户名

repl_password=000000

repl_user=repl

[server1]

hostname=server01

port=3306

[server2]

hostname=server02

candidate_master=1

port=3306

check_repl_delay=0

[server3]

hostname=server03

port=3306

[server4]

hostname=server04

port=3306

配置故障转移脚本:

vim /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 = '192.168.96.100'; # 写入VIP

my $key = "1"; #非keepalived方式切换脚本使用的

my $ssh_start_vip = "/sbin/ifconfig ens32:$key $vip";

my $ssh_stop_vip = "/sbin/ifconfig ens32:$key down"; #那么这里写服务的开关命令

$ssh_user = "root";

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" ) {

# $orig_master_host, $orig_master_ip, $orig_master_port are passed.

# If you manage master ip address at global catalog database,

# invalidate orig_master_ip here.

my $exit_code = 1;

#eval {

# print "Disabling the VIP on old master: $orig_master_host \n";

# &stop_vip();

# $exit_code = 0;

#};

eval {

print "Disabling the VIP on old master: $orig_master_host \n";

#my $ping=`ping -c 1 10.0.0.13 | grep "packet loss" | awk -F',' '{print $3}' | awk '{print $1}'`;

#if ( $ping le "90.0%"&& $ping gt "0.0%" ){

#$exit_code = 0;

#}

#else {

&stop_vip();

# updating global catalog, etc

$exit_code = 0;

#}

};

if ($@) {

warn "Got Error: $@\n";

exit $exit_code;

}

exit $exit_code;

}

elsif ( $command eq "start" ) {

# all arguments are passed.

# If you manage master ip address at global catalog database,

# activate new_master_ip here.

# You can also grant write access (create user, set read_only=0, etc) here.

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

`ssh $ssh_user\@$orig_master_ip \" $ssh_start_vip \"`;

exit 0;

}

else {

&usage();

exit 1;

}

}

# A simple system call that enable the VIP on the new master

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

chmod +x /usr/local/bin/master_ip_failover     //添加可执行权限

设置从库relay log的清除方法(server05-07):

mysql -uroot -p000000 -e 'set global relay_log_purge=0;'

mysql mha部署_MySQL高可用MHA环境部署

检查MHA ssh 通信状态:

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

mysql mha部署_MySQL高可用MHA环境部署

检查整个集群的状态:

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

mysql mha部署_MySQL高可用MHA环境部署

VIP配置管理:

通过命令方式管理VIP地址:

打开在前面编辑过的文件/etc/masterha/app1.cnf,检查如下行是否正确,再检查集群状态。