MYSQL高可用架构之MHA

最新推荐文章于 2024-07-24 17:22:53 发布
最新推荐文章于 2024-07-24 17:22:53 发布
阅读量471 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/aaaaaab_/article/details/81532647
版权

本篇博客内容写的有点赘余，
读者可以参考https://blog.csdn.net/aaaaaab_/article/details/81583657
实验环境的搭建：

准备： 在主从复制(GTID)的基础上面去做一主两从,必须保证一主二从可以实时
同步数据。
主从复制可以参考
https://blog.csdn.net/aaaaaab_/article/details/81515111
server1：172.25.38.1（master）
server2：172.25.38.2（slave）
server3：172.25.38.3（slave）
server4：172.25.38.4（mha）

在server1:

[root@server1 MHA]# ls
master_ip_failover
master_ip_online_change
mha4mysql-manager-0.56-0.el6.noarch.rpm
mha4mysql-node-0.56-0.el6.noarch.rpm
perl-Config-Tiny-2.12-7.1.el6.noarch.rpm
perl-Email-Date-Format-1.002-5.el6.noarch.rpm
perl-Log-Dispatch-2.27-1.el6.noarch.rpm
perl-Mail-Sender-0.8.16-3.el6.noarch.rpm
perl-Mail-Sendmail-0.79-12.el6.noarch.rpm
perl-MIME-Lite-3.027-2.el6.noarch.rpm
perl-MIME-Types-1.28-2.el6.noarch.rpm
perl-Parallel-ForkManager-0.7.9-1.el6.noarch.rpm
send_report
[root@server1 MHA]# yum install mha4mysql-node-0.56-0.el6.noarch.rpm -y

这里写图片描述

[root@server1 .ssh]# ssh-keygen 
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
/root/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
72:c7:15:ad:e4:17:bb:b0:a3:0f:15:48:d8:45:f0:4d root@server1
The key's randomart image is:
+--[ RSA 2048]----+
|         oo++.E  |
|        ...o.+o  |
|          .o+..o |
|         . .+.o  |
|      . S o .+ . |
|       o . .o .  |
|          .. .   |
|          ..     |
|           ..    |
+-----------------+
[root@server1 .ssh]# ls
id_rsa  id_rsa.pub  known_hosts

这里写图片描述

[root@server1 .ssh]# ssh-copy-id root@172.25.38.3
root@172.25.38.3's password: 
Now try logging into the machine, with "ssh 'root@172.25.38.3'", and check in:

  .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

[root@server1 .ssh]# ssh-copy-id root@172.25.38.2
Now try logging into the machine, with "ssh 'root@172.25.38.2'", and check in:

  .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.

这里写图片描述
在server2:

[root@server2 MHA]# ls
master_ip_failover
master_ip_online_change
mha4mysql-manager-0.56-0.el6.noarch.rpm
mha4mysql-node-0.56-0.el6.noarch.rpm
perl-Config-Tiny-2.12-7.1.el6.noarch.rpm
perl-Email-Date-Format-1.002-5.el6.noarch.rpm
perl-Log-Dispatch-2.27-1.el6.noarch.rpm
perl-Mail-Sender-0.8.16-3.el6.noarch.rpm
perl-Mail-Sendmail-0.79-12.el6.noarch.rpm
perl-MIME-Lite-3.027-2.el6.noarch.rpm
perl-MIME-Types-1.28-2.el6.noarch.rpm
perl-Parallel-ForkManager-0.7.9-1.el6.noarch.rpm
send_report
[root@server2 MHA]# yum install mha4mysql-node-0.56-0.el6.noarch.rpm -y

这里写图片描述

[root@server2 MHA]# ssh-keygen 
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
f9:df:dc:8e:9f:b1:69:50:77:88:a8:63:3b:f0:da:7f root@server2
The key's randomart image is:
+--[ RSA 2048]----+
|                 |
|                 |
|           . . . |
|         .. . ..o|
|        S.    . o|
|      . +.   .   |
|       + o.   .. |
|       .+  .Eo +=|
|      ...o... =*+|
+-----------------+

这里写图片描述

[root@server2 MHA]# ssh-copy-id 172.25.38.1
[root@server2 MHA]# ssh-copy-id 172.25.38.3

这里写图片描述

[root@server2 MHA]# mysql -p
mysql> grant replication slave on *.* to yiyi@'172.25.38.%' identified by 'YIYI=bushe24';
Query OK, 0 rows affected, 1 warning (0.00 sec)

这里写图片描述
在server3重新配置slave数据库的初始化：

[root@server3 ~]# ls
MHA
[root@server3 ~]# cd MHA/
[root@server3 MHA]# ls
master_ip_failover
master_ip_online_change
mha4mysql-manager-0.56-0.el6.noarch.rpm
mha4mysql-node-0.56-0.el6.noarch.rpm
perl-Config-Tiny-2.12-7.1.el6.noarch.rpm
perl-Email-Date-Format-1.002-5.el6.noarch.rpm
perl-Log-Dispatch-2.27-1.el6.noarch.rpm
perl-Mail-Sender-0.8.16-3.el6.noarch.rpm
perl-Mail-Sendmail-0.79-12.el6.noarch.rpm
perl-MIME-Lite-3.027-2.el6.noarch.rpm
perl-MIME-Types-1.28-2.el6.noarch.rpm
perl-Parallel-ForkManager-0.7.9-1.el6.noarch.rpm
send_report
[root@server3 MHA]# yum install mha4mysql-node-0.56-0.el6.noarch.rpm -y

这里写图片描述

[root@server3 ~]# ssh-keygen 
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
2b:8b:36:e7:dc:aa:b0:65:10:13:9b:62:b4:16:c2:3f root@server3
The key's randomart image is:
+--[ RSA 2048]----+
|oo.              |
|o.o+             |
|.+*              |
|o. E             |
|  . .   S        |
|   .     .       |
|  . o . .        |
|   =oo.+         |
|  ..o==..        |
+-----------------+

这里写图片描述

[root@server3 ~]# ssh-copy-id 172.25.38.1
[root@server3 ~]# ssh-copy-id 172.25.38.2

这里写图片描述

mysql> grant replication slave on *.* to yiyi@'172.25.38.%' identified by 'YIYI=bushe24';
Query OK, 0 rows affected, 1 warning (0.00 sec)

这里写图片描述
在server4（mha主机）：

[root@server4 ~]# ls
MHA
[root@server4 ~]# cd MHA/
[root@server4 MHA]# ls
master_ip_failover
master_ip_online_change
mha4mysql-manager-0.56-0.el6.noarch.rpm
mha4mysql-node-0.56-0.el6.noarch.rpm
perl-Config-Tiny-2.12-7.1.el6.noarch.rpm
perl-Email-Date-Format-1.002-5.el6.noarch.rpm
perl-Log-Dispatch-2.27-1.el6.noarch.rpm
perl-Mail-Sender-0.8.16-3.el6.noarch.rpm
perl-Mail-Sendmail-0.79-12.el6.noarch.rpm
perl-MIME-Lite-3.027-2.el6.noarch.rpm
perl-MIME-Types-1.28-2.el6.noarch.rpm
perl-Parallel-ForkManager-0.7.9-1.el6.noarch.rpm
send_report
[root@server4 MHA]# yum install * -y

这里写图片描述

mkdir /etc/mha                 ##创建工作目录workdir
mkdir /etc/mha                       ##创建配置文件所在目录
cd /etc/mha/     
vim app.conf
[root@server4 mha]# cat app.conf 
[server default]

manager_workdir=/usr/local/bingrep master_ip_failover /etc/masterha/app1.cnf

manager_log=/usr/local/bin/mha.log

master_binlog_dir=/var/lib/mysql

#master_ip_failover_script=/usr/local/bin/master_ip_failover

master_ip_online_change_script=/usr/local/bin/master_ip_online_change

user=root

password=Aa@+123456

ping_interval=1

remote_workdir=/tmp

repl_user=yiyi

repl_password=YIYI+bushe24

report_script=/usr/local/send_report

#secondary_check_script=/usr/local/bin/masterha_secondary_check -s server03 -s server02

#shutdown_script=""

ssh_user=root



[server1]

hostname=172.25.38.1

port=3306



[server2]

hostname=172.25.38.2

port=3306

candidate_master=1

check_repl_delay=0



[server3]

hostname=172.25.38.3

port=3306

#no_master=1

这里写图片描述

[root@server4 mha]# masterha_check_ssh --conf=/etc/mha/app.conf 
Thu Aug  9 15:40:10 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Aug  9 15:40:10 2018 - [info] Reading application default configuration from /etc/mha/app.conf..
Thu Aug  9 15:40:10 2018 - [info] Reading server configuration from /etc/mha/app.conf..
Thu Aug  9 15:40:10 2018 - [info] Starting SSH connection tests..
Thu Aug  9 15:40:11 2018 - [debug] 
Thu Aug  9 15:40:10 2018 - [debug]  Connecting via SSH from root@172.25.38.1(172.25.38.1:22) to root@172.25.38.2(172.25.38.2:22)..
Thu Aug  9 15:40:11 2018 - [debug]   ok.
Thu Aug  9 15:40:11 2018 - [debug]  Connecting via SSH from root@172.25.38.1(172.25.38.1:22) to root@172.25.38.3(172.25.38.3:22)..
Thu Aug  9 15:40:11 2018 - [debug]   ok.
Thu Aug  9 15:40:12 2018 - [debug] 
Thu Aug  9 15:40:11 2018 - [debug]  Connecting via SSH from root@172.25.38.2(172.25.38.2:22) to root@172.25.38.1(172.25.38.1:22)..
Thu Aug  9 15:40:11 2018 - [debug]   ok.
Thu Aug  9 15:40:11 2018 - [debug]  Connecting via SSH from root@172.25.38.2(172.25.38.2:22) to root@172.25.38.3(172.25.38.3:22)..
Thu Aug  9 15:40:12 2018 - [debug]   ok.
Thu Aug  9 15:40:12 2018 - [debug] 
Thu Aug  9 15:40:11 2018 - [debug]  Connecting via SSH from root@172.25.38.3(172.25.38.3:22) to root@172.25.38.1(172.25.38.1:22)..
Thu Aug  9 15:40:12 2018 - [debug]   ok.
Thu Aug  9 15:40:12 2018 - [debug]  Connecting via SSH from root@172.25.38.3(172.25.38.3:22) to root@172.25.38.2(172.25.38.2:22)..
Thu Aug  9 15:40:12 2018 - [debug]   ok.
Thu Aug  9 15:40:12 2018 - [info] All SSH connection tests passed successfully

这里写图片描述
通过脚本检测状态：

[root@server4 mha]# touch /usr/local/bin/master_ip_failover
[root@server4 mha]# cd /usr/local/bin/
[root@server4 bin]# touch /usr/local/bin/master_ip_online_change
[root@server4 bin]# vim master_ip_failover 
[root@server4 bin]# vim master_ip_online_change 
[root@server4 bin]# chmod +x master_ip_failover 
[root@server4 bin]# chmod +x master_ip_online_change

这里写图片描述
保证三台虚拟机的/etc/my.cnf一致server-id区分即可，在每个虚拟机重启服务即可

[root@server1 ~]# scp /etc/my.cnf server2:/etc/my.cnf
The authenticity of host 'server2 (172.25.38.2)' can't be established.
RSA key fingerprint is 2f:cc:a7:97:6a:d8:41:5b:90:f3:91:b6:e8:87:4c:b3.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'server2' (RSA) to the list of known hosts.
my.cnf                                                               100% 1034     1.0KB/s   00:00    
[root@server1 ~]# scp /etc/my.cnf server3:/etc/my.cnf
my.cnf                                                               100% 1034     1.0KB/s   00:00

这里写图片描述
开启MHA Manager监控

[root@server4 bin]# masterha_check_repl --conf=/etc/mha/app.conf
Thu Aug  9 23:48:32 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Aug  9 23:48:32 2018 - [info] Reading application default configuration from /etc/mha/app.conf..
Thu Aug  9 23:48:32 2018 - [info] Reading server configuration from /etc/mha/app.conf..
Thu Aug  9 23:48:32 2018 - [info] MHA::MasterMonitor version 0.56.
Thu Aug  9 23:48:32 2018 - [info] GTID failover mode = 1
Thu Aug  9 23:48:32 2018 - [info] Dead Servers:
Thu Aug  9 23:48:32 2018 - [info] Alive Servers:
Thu Aug  9 23:48:32 2018 - [info]   172.25.254.1(172.25.254.1:3306)
Thu Aug  9 23:48:32 2018 - [info]   172.25.254.2(172.25.254.2:3306)
Thu Aug  9 23:48:32 2018 - [info]   172.25.254.3(172.25.254.3:3306)
Thu Aug  9 23:48:32 2018 - [info] Alive Slaves:
Thu Aug  9 23:48:32 2018 - [info]   172.25.254.2(172.25.254.2:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Aug  9 23:48:32 2018 - [info]     GTID ON
Thu Aug  9 23:48:32 2018 - [info]     Replicating from 172.25.254.1(172.25.254.1:3306)
Thu Aug  9 23:48:32 2018 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Aug  9 23:48:32 2018 - [info]   172.25.254.3(172.25.254.3:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Aug  9 23:48:32 2018 - [info]     GTID ON
Thu Aug  9 23:48:32 2018 - [info]     Replicating from 172.25.254.1(172.25.254.1:3306)
Thu Aug  9 23:48:32 2018 - [info] Current Alive Master: 172.25.254.1(172.25.254.1:3306)
Thu Aug  9 23:48:32 2018 - [info] Checking slave configurations..
Thu Aug  9 23:48:32 2018 - [info]  read_only=1 is not set on slave 172.25.254.2(172.25.254.2:3306).
Thu Aug  9 23:48:32 2018 - [info]  read_only=1 is not set on slave 172.25.254.3(172.25.254.3:3306).
Thu Aug  9 23:48:32 2018 - [info] Checking replication filtering settings..
Thu Aug  9 23:48:32 2018 - [info]  binlog_do_db= , binlog_ignore_db= 
Thu Aug  9 23:48:32 2018 - [info]  Replication filtering check ok.
Thu Aug  9 23:48:32 2018 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Thu Aug  9 23:48:32 2018 - [info] Checking SSH publickey authentication settings on the current master..
Thu Aug  9 23:48:32 2018 - [info] HealthCheck: SSH to 172.25.254.1 is reachable.
Thu Aug  9 23:48:32 2018 - [info] 
172.25.254.1(172.25.254.1:3306) (current master)
 +--172.25.254.2(172.25.254.2:3306)
 +--172.25.254.3(172.25.254.3:3306)

Thu Aug  9 23:48:32 2018 - [info] Checking replication health on 172.25.254.2..
Thu Aug  9 23:48:32 2018 - [info]  ok.
Thu Aug  9 23:48:32 2018 - [info] Checking replication health on 172.25.254.3..
Thu Aug  9 23:48:32 2018 - [info]  ok.
Thu Aug  9 23:48:32 2018 - [warning] master_ip_failover_script is not defined.
Thu Aug  9 23:48:32 2018 - [warning] shutdown_script is not defined.
Thu Aug  9 23:48:32 2018 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

这里写图片描述

[root@server4 bin]# cat /etc/mha/app.conf 
[server default]
manager_workdir=/etc/mha
manager_log=/usr/local/bin/mha.log
master_binlog_dir=/var/lib/mysql
#master_ip_failover_script=/usr/local/bin/master_ip_failover
master_ip_online_change_script=/usr/local/bin/master_ip_online_change
user=root
password=Aa@+123456
ping_interval=1
remote_workdir=/tmp
repl_user=repl
repl_password=Yakexi+007
report_script=/usr/local/send_report
#secondary_check_script=/usr/local/bin/masterha_secondary_check -s server03 -s server02
#shutdown_script=""
ssh_user=root
[server1]
hostname=172.25.254.1
port=3306
[server2]
hostname=172.25.254.2
port=3306
candidate_master=1
check_repl_delay=0
[server3]
hostname=172.25.254.3
port=3306
#no_master=1

这里写图片描述
通过master_check_status脚本查看Manager的状态

[root@server4 bin]# masterha_check_status --conf=/etc/mha/app.conf
app is stopped(2:NOT_RUNNING).
解决报错打开监控即可
[root@server4 bin]# nohup masterha_manager --conf=/etc/mha/app.conf --remove_dead_master_conf --ignore_last_failover < /dev/null > /usr/local/mha/mha.log 2>&1 & 
[1] 1646
[root@server4 bin]# masterha_check_status --conf=/etc/mha/app.confapp (pid:1646) is running(0:PING_OK), master:172.25.254.1

这里写图片描述
查看日志会出来成功：

[root@server4 bin]# tail -10 /usr/local/bin/mha.log
172.25.254.1(172.25.254.1:3306) (current master)
 +--172.25.254.2(172.25.254.2:3306)
 +--172.25.254.3(172.25.254.3:3306)

Thu Aug  9 23:52:03 2018 - [warning] master_ip_failover_script is not defined.
Thu Aug  9 23:52:03 2018 - [warning] shutdown_script is not defined.
Thu Aug  9 23:52:03 2018 - [info] Set master ping interval 1 seconds.
Thu Aug  9 23:52:03 2018 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Thu Aug  9 23:52:03 2018 - [info] Starting ping health check on 172.25.254.1(172.25.254.1:3306)..
Thu Aug  9 23:52:03 2018 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

这里写图片描述

[root@server4 ~]# vim /etc/mha/app.conf    
master_ip_failover_script=/usr/local/bin/master_ip_failover
master_ip_online_change_script=/usr/local/bin/master_ip_online_change
#将注释的两行打开，脚本拷到指定位置

分享两个脚本都需要更改虚拟IP：

[root@server4 bin]# cat 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 = '172.25.254.100/24';
my $key = '1';
my $ssh_start_vip = "/sbin/ifconfig eth0:$key $vip";
my $ssh_stop_vip = "/sbin/ifconfig eth0:$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";
}
[root@server4 bin]# cat master_ip_online_change 
#!/usr/bin/env perl
use strict;  
use warnings FATAL =>'all';  

use Getopt::Long;  

my $vip = '172.25.254.100/24';  # Virtual IP  
my $key = "1";  
my $ssh_start_vip = "/sbin/ifconfig eth0:$key $vip";  
my $ssh_stop_vip = "/sbin/ifconfig eth0:$key down";  
my $exit_code = 0;  

my (  
  $command,              $orig_master_is_new_slave, $orig_master_host,  
  $orig_master_ip,       $orig_master_port,         $orig_master_user,  
  $orig_master_password, $orig_master_ssh_user,     $new_master_host,  
  $new_master_ip,        $new_master_port,          $new_master_user,  
  $new_master_password,  $new_master_ssh_user,  
);  
GetOptions(  
  'command=s'                => \$command,  
  'orig_master_is_new_slave' => \$orig_master_is_new_slave,  
  'orig_master_host=s'       => \$orig_master_host,  
  'orig_master_ip=s'         => \$orig_master_ip,  
  'orig_master_port=i'       => \$orig_master_port,  
  'orig_master_user=s'       => \$orig_master_user,  
  'orig_master_password=s'   => \$orig_master_password,  
  'orig_master_ssh_user=s'   => \$orig_master_ssh_user,  
  '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,  
  'new_master_ssh_user=s'    => \$new_master_ssh_user,  
);  


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 "\n\n\n***************************************************************\n";  
            print "Disabling the VIP - $vip on old master: $orig_master_host\n";  
            print "***************************************************************\n\n\n\n";  
&stop_vip();  
            $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 "\n\n\n***************************************************************\n";  
            print "Enabling the VIP - $vip on new master: $new_master_host \n";  
            print "***************************************************************\n\n\n\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 $orig_master_ssh_user\@$orig_master_host \" $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 $new_master_ssh_user\@$new_master_host \" $ssh_start_vip \"`;  
}  
# A simple system call that disable the VIP on the old_master  
sub stop_vip() {  
`ssh $orig_master_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@server1 etc]# /etc/init.d/mysqld stop  将主端关闭mysql
Stopping mysqld:                                           [  OK  ]
[root@server1 etc]#

server2会出来顶替成为主端：

[root@server2 MHA]# mysql -pAa@+123456
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 46
Server version: 5.7.17-log MySQL Community Server (GPL)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show master status;
+------------------+----------+--------------+------------------+----------------------------------------------------------------------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set                                                                |
+------------------+----------+--------------+------------------+----------------------------------------------------------------------------------+
| mysql-bin.000001 |      445 |              |                  | bac7ebff-9bde-11e8-8767-5254004b3455:1-2,
c152f584-9bde-11e8-a530-525400e41981:1 |
+------------------+----------+--------------+------------------+----------------------------------------------------------------------------------+
1 row in set (0.00 sec)

mysql> show slave status\G
Empty set (0.00 sec)

这里写图片描述
将server1重新打开还是主端：

[root@server1 etc]# /etc/init.d/mysqld start
Starting mysqld:                                           [  OK  ]
[root@server1 etc]# mysql -pAa@+123456
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.7.17-log MySQL Community Server (GPL)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> show master status;
+------------------+----------+--------------+------------------+------------------------------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set                        |
+------------------+----------+--------------+------------------+------------------------------------------+
| mysql-bin.000003 |      194 |              |                  | bac7ebff-9bde-11e8-8767-5254004b3455:1-2 |
+------------------+----------+--------------+------------------+------------------------------------------+
1 row in set (0.00 sec)

mysql> show slave status\G
Empty set (0.00 sec)

这里写图片描述

Logbook怪
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
MySQL之MHA高可用
提升自己
10-10 1442
MySQL服务器中，单台服务器无法承载服务量就配置多台MySQL服务器，多台MySQL服务器或者MySQL服务器无冗余的情况下，配置主从复制。MySQL服务器的读和写的压力不均衡可使用MySQL的读写分离，MySQL的读写分离中Master存在单点故障，就得用到MHAMHA（Master High Availability）是一套优秀的MySQL高可用环境下故障切换和主从复制的软件MHA的出现就是解决MySQL单点故障的问题MySQL故障切换过程中，MHA能做到0-30秒内自动完成故障切换操作。
MySQL高可用架构之MHA
wjl7813的博客
01-27 295
MHA是什么？ MHA是由日本Mysql yoshinorim专家（原就职于DeNA现就职于FaceBook）用Perl写的一套Mysql故障切换方案，来保障数据库的高可用性，它的功能是能在0-30s之内实现主Mysql故障转移（failover），MHA故障转移可以很好的帮我们解决从库数据的一致性问题，同时最大化挽回故障发生后数据的一致性。 官方网站：https://code.google.
mysql高可用架构
08-22 129
高可用 高可用(High Availabiltity) 应用提供持续不间断(可用)的服务的能力 系统高可用性的评价通常用可用率表示 造成不可用的原因 硬件故障(各种) 预期中的系统软硬件维护 软件缺陷(应用代码，服务程序都可能存在bug) 攻击，泄露，认为失误...等安全事件 对于系统来说，不可用时间是各关键组件不可用时间的总和...
MySQL的高可用(MHA)
最新发布
2402_84868182的博客
07-24 1172
一旦检测到主库故障，MHA 会选择一个最新的从库，并执行一系列操作将其提升为主库，包括应用剩余的 binlog 等。总之，MHA 为 MySQL 提供了一种可靠的高可用解决方案，但在实际应用中需要仔细配置和维护，以确保其正常稳定运行。设置为"true"表示从服务器会记录自己执行的更改操作，将其写入从服务器的二进制日志文件中。指定主服务器（master）的二进制日志文件名称，用于记录主服务器上的更改操作的日志文件。指定从服务器的中继日志文件名称，即用于记录主服务器的二进制日志在从服务器上执行的中继日志。
Mysql高可用架构
MrLee的博客
04-17 489
一，什么是高可用 高可用性H.A. ( High Availability )指的是通过尽量缩短因日常维护操作(计划)和突发的系统崩溃(非计划)所导致的停机时间，以提高系统和应用的可用性。 而在实际生产中有好多原因都可能引起数据库系统的不可用。 如： 严重的主从延迟 主从复制中断 锁引起的大量阻塞 这些情况下虽然不至于完全不可用，但是已经不是高可用了，更不用说软硬件故障造成的服务器宕机等...
MySQL高可用架构
m0_50180963的博客
04-22 205
引言 “高可用”是互联网一个永恒的话题，先避开MySQL不谈，为了保证各种服务的高可用有几种常用的解决方案。 服务冗余：把服务部署多份，当某个节点不可用时，切换到其他节点。服务冗余对于无状态的服务是相对容易的。 服务备份：有些服务是无法同时存在多个运行时的，比如说：Nginx的反向代理，一些集群的leader节点。这时可以存在一个备份服务，处于随时待命状态。 自动切换：服务冗余之后，当某个节点不可用时，要做到快速切换。 总结起来就是 冗余+故障转移。 MySQL高可用 MySQL的高可用也是同样
MySQL高可用架构MHA
01-09
MHA工作原理 部署MHA 1.配置四台主机ssh登录不用密码 ssh-keygen -t rsa ssh-copy-id 192.168.100.10（20.30.102） 2.上传安装包，解压编译安装 配置yum仓库 vim /etc/yum.repos.d/mhapath.repo ##进入yum仓库，...
MySQL高可用架构MHA软件包及脚本
12-21
MySQL高可用架构（MHA，Master High Availability）是一款用于MySQL集群的开源工具，旨在提高数据库系统的可用性和稳定性。MHA的主要目标是通过监控主库（Master）的状态，并在主库出现故障时，自动将从库（Slave）...
mysql 切换用户_浅谈MySQL集群高可用架构
weixin_39557419的博客
11-06 73
前言高可用架构对于互联网服务基本是标配，无论是应用服务还是数据库服务都需要做到高可用。对于一个系统而言，可能包含很多模块，比如前端应用，缓存，数据库，搜索，消息队列等，每个模块都需要做到高可用，才能保证整个系统的高可用。对于数据库服务而言，高可用可能更复杂，对用户的服务可用，不仅仅是能访问，还需要有正确性保证，因此数据库的高可用方案是一直以来的讨论热点，今天就各种的高可用方案，谈一下个人的一些看法...
33.MySQL高可用架构
weixin_30682127的博客
07-25 217
33.高可用架构33.1 MMM架构MMM(Master-Master replication manager for MySQL)是一套支持双主故障切换和双主日常管理的脚本程序(Perl)。主要用来监控和管理MySQL Master-Master双主复制。优点：故障切换、多个Slave的read负载均衡。缺点：无法完全保证数据一致性。 33.2 MHA架构MHA(Master High Ava...
mysql高可用架构设计
sinat_34814635的博客
03-04 1155
数据库中的数据在主库完成更新后，是异步同步到每个从库上的，这个过程有一个微小的时间差，这个时间差叫主从同步延迟。正常情况下，主从延迟非常小，不超过 1ms。但即使这个非常小的延迟，也会导致在某一个时刻，主库和从库上的数据是不一致的。应用程序需要能接受并克服这种主从不一致的情况，否则就会引发一些由于主从延迟导致的数据错误。主备切换可能是一个主动运维动作，比如软件升级、主库所在机器按计划下线等，也可能是被动操作，比如主库所在机器掉电。接下来，我们先一起看看主动切换的场景。
​老生常谈：MySQL高可用架构
m0_64374605的博客
12-15 5136
引言 “高可用”是互联网一个永恒的话题，先避开MySQL不谈，为了保证各种服务的高可用有几种常用的解决方案。 服务冗余：把服务部署多份，当某个节点不可用时，切换到其他节点。服务冗余对于无状态的服务是相对容易的。 服务备份：有些服务是无法同时存在多个运行时的，比如说：Nginx的反向代理，一些集群的leader节点。这时可以存在一个备份服务，处于随时待命状态。 自动切换：服务冗余之后，当某个节点不可用时，要做到快速切换。 总结起来就是冗余+故障转移。 MySQL高可用 MySQL的高可用也是同..
MySQL5.7新特性--官方高可用方案MGR介绍
weixin_38166686的博客
12-15 266
MGR简介 MySQL Group Replication（下简称：MGR）是MySQL官方推出的一种基于Paxos协议的状态机复制。在MGR出现之前，用户常见的MySQL高可用方式，无论怎么变化架构，本质就是Master-Slave架构。MySQL 5.7版本开始支持无损半同步复制（lossless semi-sync replication），从而进一步提示数据复制的强一致...
MySQL高可用MHA
芦苇的博客
07-02 181
内容概要一、MHA的概念1、MHA组成2、MHA特点二、搭建MySQL+MHA1、修改mysql节点的主机名2、修改三台MySQL服务器的主配置文件/etc/my.cnf，并创建命令软链接3、配置MySQL一主两从（1）所有MySQL服务器进行MySQL授权（2）在Master节点查看二进制文件和同步点（3）在 Slave1、Slave2 节点执行同步操作（4）Slave1、Slave2 节点设置为只读模式（5）主从复制验证4、安装 MHA 软件（1）所有服务器上都安装 MHA 依赖的环境（2）安装MHA
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值