MHA+Keepalived

最新推荐文章于 2022-09-09 16:21:03 发布
最新推荐文章于 2022-09-09 16:21:03 发布
阅读量2.9k 收藏 1
点赞数
分类专栏： MySQL 文章标签： MHA keepalived
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u014674448/article/details/51898909
版权

一：MHA的部署参考：简单粗暴的MHA部署

二：MHA结合Keepalived以使MySQL高可用对应用透明
1.Keepalived的Download&INSTALL
Download Keepalived 

INSTALL For Keepalived
tar zxvf keepalived.xxx
cd keepalivedxxx
./configure --prefix=/usr/local/keepalived
make && make install 

configure: error:
  !!! OpenSSL is not properly installed on your system. !!!
  !!! Can not include OpenSSL headers files.            !!!
解决：yum install openssl-devel

2.Keepalived的configuration

[root@db-two keepalived-1.2.20]# cp /usr/local/keepalived/etc/rc.d/init.d/keepalived  /etc/rc.d/init.d/
[root@db-two keepalived-1.2.20]# cp /usr/local/keepalived/etc/sysconfig/keepalived  /etc/sysconfig/
[root@db-two keepalived-1.2.20]# mkdir /etc/keepalived
[root@db-two keepalived-1.2.20]# cp /usr/local/keepalived/etc/keepalived/keepalived.conf  /etc/keepalived/
[root@db-two keepalived-1.2.20]# cp /usr/local/keepalived/sbin/keepalived   /usr/sbin/

vim /etc/keepalived/keepalived.conf
MASTER
[root@db-three keepalived-1.2.20]# cat  /etc/keepalived/keepalived.conf
global_defs {
 router_id mysql-master #修改为自己的主机名
 notification_email {
 gyc1412@163.com   #接收邮件，可以有多个，一行一个
}
 #当主、备份设备发生改变时，通过邮件通知
 notification_email_from coral1213@126.com
 #发送邮箱服务器
 smtp_server stmp.163.com
 #发送邮箱超时时间
 smtp_connect_timeout 30
 }
##################第一部分###################
vrrp_instance VI_1 {
     state BACKUP    #都修改成BACKUP
     interface eth0    #绑定的网卡
     virtual_router_id 60 #默认51 主从都修改为60
     priority 100            #优先级，在mysql-slave上LVS上修改成80，即master>slave
     advert_int 1
     nopreempt #不抢占资源，意思就是它活了之后也不会再把主抢回来

     authentication {
     # 认证方式，可以是PASS或AH两种认证方式
     auth_type PASS
     # 认证密码
     auth_pass 1111
     }
virtual_ipaddress {
     192.168.1.100
     }
}
##################第二部分###################
virtual_server 192.168.1.100 3306 {
     delay_loop 6
     lb_algo wrr
     lb_kind DR
     nat_mask 255.255.255.0
     persistence_timeout 50
     protocol TCP
    real_server 192.168.1.30 3306 {
     weight 1
     TCP_CHECK {
         connect_timeout 10
         nb_get_retry 3
         connect_port 3306
         }
     }
}


SLAVE
[root@db-two keepalived-1.2.20]# cat  /etc/keepalived/keepalived.conf
global_defs {
 router_id mysql-master #修改为自己的主机名
 notification_email {
 gyc1412@163.com   #接收邮件，可以有多个，一行一个
}
 #当主、备份设备发生改变时，通过邮件通知
 notification_email_from coral1213@126.com
 #发送邮箱服务器
 smtp_server stmp.163.com
 #发送邮箱超时时间
 smtp_connect_timeout 30
 }
##################第一部分###################
vrrp_instance VI_1 {
     state BACKUP    #都修改成BACKUP
     interface eth0    #绑定的网卡
     virtual_router_id 60 #默认51 主从都修改为60
     priority 80            #优先级，在mysql-slave上LVS上修改成80
     advert_int 1
     nopreempt #不抢占资源，意思就是它活了之后也不会再把主抢回来

     authentication {
     # 认证方式，可以是PASS或AH两种认证方式
     auth_type PASS
     # 认证密码
     auth_pass 1111
     }
virtual_ipaddress {
     192.168.1.100
     }
}
##################第二部分###################
virtual_server 192.168.1.100 3306 {
     delay_loop 6
     lb_algo wrr
     lb_kind DR
     nat_mask 255.255.255.0
     persistence_timeout 50
     protocol TCP
    real_server 192.168.1.20 3306 {
     weight 1
     TCP_CHECK {
         connect_timeout 10
         nb_get_retry 3
         connect_port 3306
         }
     }
}

Manager For Keepalived
/etc/init.d/keepalived start
/etc/init.d/keepalived stop
/etc/init.d/keepalived status
Keepalived的日志在/var/log/messages
注意：Keepalived的启动顺序对VIP绑定的影响?

3.对简单粗暴的MHA部署 mha.conf修改如下

[server default]
manager_workdir=/usr/local/mha
master_ip_failover_script=/usr/local/mha/script/master_ip_failover     #master_ip_failover、master_ip_online_change、send_report脚本是由mha4mysql-manager源码包中sample/script下拷贝的
master_ip_online_change_script=/usr/local/mha/script/master_ip_online_change
password=123
remote_workdir=/usr/local/mha
repl_password=passwd
repl_user=slave
report_script=/usr/local/mha/script/send_report
shutdown_script=""
ssh_user=root
user=root

[server1]
candidate_master=1
check_repl_delay=0
hostname=192.168.1.20

[server2]
hostname=192.168.1.30


[server3]
hostname=192.168.1.40

4.对mha.conf中提到的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.1.100';
my $ssh_start_vip = "/etc/init.d/keepalived start";
my $ssh_stop_vip = "/etc/init.d/keepalived stop";

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";
        #`ssh $ssh_user\@cluster1 \" $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() {
     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";
}

三：MHA+Keepalived的Failover测试以及相关日志信息如下

[root@db-three keepalived-1.2.20]# /etc/init.d/mysqld  stop
Stopping mysqld:                                           [  OK  ]
[root@db-three keepalived-1.2.20]# tail -f /var/log/messages
Jul  7 11:43:39 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) Entering MASTER STATE
Jul  7 11:43:39 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) setting protocol VIPs.
Jul  7 11:43:39 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 192.168.1.100
Jul  7 11:43:39 db-three Keepalived_healthcheckers[8271]: Netlink reflector reports IP 192.168.1.100 added
Jul  7 11:43:44 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 192.168.1.100
Jul  7 11:56:23 db-three Keepalived_healthcheckers[8271]: TCP connection to [192.168.1.30]:3306 failed.
Jul  7 11:56:24 db-three Keepalived_healthcheckers[8271]: TCP connection to [192.168.1.30]:3306 failed.
Jul  7 11:56:24 db-three Keepalived_healthcheckers[8271]: Check on service [192.168.1.30]:3306 failed after 1 retry.
Jul  7 11:56:24 db-three Keepalived_healthcheckers[8271]: Removing service [192.168.1.30]:3306 from VS [192.168.1.100]:3306
Jul  7 11:56:24 db-three Keepalived_healthcheckers[8271]: Lost quorum 1-0=1 > 0 for VS [192.168.1.100]:3306
Jul  7 11:56:38 db-three Keepalived[8269]: Stopping
Jul  7 11:56:38 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) sent 0 priority
Jul  7 11:56:38 db-three Keepalived_vrrp[8272]: VRRP_Instance(VI_1) removing protocol VIPs.
Jul  7 11:56:38 db-three Keepalived_healthcheckers[8271]: Netlink reflector reports IP 192.168.1.100 removed
Jul  7 11:56:38 db-three Keepalived_healthcheckers[8271]: Stopped
Jul  7 11:56:39 db-three Keepalived_vrrp[8272]: Stopped
Jul  7 11:56:39 db-three Keepalived[8269]: Stopped Keepalived v1.2.20 (07/07,2016)

slave的keepalived日志信息
[root@db-two keepalived-1.2.20]# tail -f /var/log/messages
Jun 21 15:05:37 db-two Keepalived_healthcheckers[10358]: Unknown keyword 'nat_mask'
Jun 21 15:05:37 db-two Keepalived_healthcheckers[10358]: Unknown keyword 'nb_get_retry'
Jun 21 15:05:37 db-two Keepalived_healthcheckers[10358]: Using LinkWatch kernel netlink reflector...
Jun 21 15:05:37 db-two Keepalived_healthcheckers[10358]: Activating healthchecker for service [192.168.1.20]:3306
Jun 21 15:15:13 db-two Keepalived_vrrp[10359]: VRRP_Instance(VI_1) Transition to MASTER STATE
Jun 21 15:15:14 db-two Keepalived_vrrp[10359]: VRRP_Instance(VI_1) Entering MASTER STATE
Jun 21 15:15:14 db-two Keepalived_vrrp[10359]: VRRP_Instance(VI_1) setting protocol VIPs.
Jun 21 15:15:14 db-two Keepalived_vrrp[10359]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 192.168.1.100
Jun 21 15:15:14 db-two Keepalived_healthcheckers[10358]: Netlink reflector reports IP 192.168.1.100 added
Jun 21 15:15:19 db-two Keepalived_vrrp[10359]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 192.168.1.100


mha的manager日志信息
Tue Jun 21 22:56:55 2016 - [warning] Got error on MySQL select ping: 2006 (MySQL server has gone away)
Tue Jun 21 22:56:55 2016 - [info] Executing SSH check script: exit 0
Tue Jun 21 22:56:55 2016 - [info] HealthCheck: SSH to 192.168.1.30 is reachable.
Tue Jun 21 22:56:58 2016 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
Tue Jun 21 22:56:58 2016 - [warning] Connection failed 2 time(s)..
Tue Jun 21 22:57:01 2016 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
Tue Jun 21 22:57:01 2016 - [warning] Connection failed 3 time(s)..
Tue Jun 21 22:57:04 2016 - [warning] Got error on MySQL connect: 2013 (Lost connection to MySQL server at 'reading initial communication packet', system error: 111)
Tue Jun 21 22:57:04 2016 - [warning] Connection failed 4 time(s)..
Tue Jun 21 22:57:04 2016 - [warning] Master is not reachable from health checker!
Tue Jun 21 22:57:04 2016 - [warning] Master 192.168.1.30(192.168.1.30:3306) is not reachable!
Tue Jun 21 22:57:04 2016 - [warning] SSH is reachable.
Tue Jun 21 22:57:04 2016 - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/mha/mha.conf again, and trying to connect to all serverrver status..
Tue Jun 21 22:57:04 2016 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jun 21 22:57:04 2016 - [info] Reading application default configuration from /etc/mha/mha.conf..
Tue Jun 21 22:57:04 2016 - [info] Reading server configuration from /etc/mha/mha.conf..
Tue Jun 21 22:57:04 2016 - [info] GTID failover mode = 1
Tue Jun 21 22:57:04 2016 - [info] Dead Servers:
Tue Jun 21 22:57:04 2016 - [info]   192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:04 2016 - [info] Alive Servers:
Tue Jun 21 22:57:04 2016 - [info]   192.168.1.20(192.168.1.20:3306)
Tue Jun 21 22:57:04 2016 - [info]   192.168.1.40(192.168.1.40:3306)
Tue Jun 21 22:57:04 2016 - [info] Alive Slaves:
Tue Jun 21 22:57:04 2016 - [info]   192.168.1.20(192.168.1.20:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:04 2016 - [info]     GTID ON
Tue Jun 21 22:57:04 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:04 2016 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 21 22:57:04 2016 - [info]   192.168.1.40(192.168.1.40:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:04 2016 - [info]     GTID ON
Tue Jun 21 22:57:04 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:04 2016 - [info] Checking slave configurations..
Tue Jun 21 22:57:04 2016 - [info]  read_only=1 is not set on slave 192.168.1.20(192.168.1.20:3306).
Tue Jun 21 22:57:04 2016 - [info]  read_only=1 is not set on slave 192.168.1.40(192.168.1.40:3306).
Tue Jun 21 22:57:04 2016 - [info] Checking replication filtering settings..
Tue Jun 21 22:57:04 2016 - [info]  Replication filtering check ok.
Tue Jun 21 22:57:04 2016 - [info] Master is down!
Tue Jun 21 22:57:04 2016 - [info] Terminating monitoring script.
Tue Jun 21 22:57:04 2016 - [info] Got exit code 20 (Master dead).
Tue Jun 21 22:57:04 2016 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jun 21 22:57:04 2016 - [info] Reading application default configuration from /etc/mha/mha.conf..
Tue Jun 21 22:57:04 2016 - [info] Reading server configuration from /etc/mha/mha.conf..
Tue Jun 21 22:57:04 2016 - [info] MHA::MasterFailover version 0.56.
Tue Jun 21 22:57:04 2016 - [info] Starting master failover.
Tue Jun 21 22:57:04 2016 - [info]
Tue Jun 21 22:57:04 2016 - [info] * Phase 1: Configuration Check Phase..
Tue Jun 21 22:57:04 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] GTID failover mode = 1
Tue Jun 21 22:57:05 2016 - [info] Dead Servers:
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info] Checking master reachability via MySQL(double check)...
Tue Jun 21 22:57:05 2016 - [info]  ok.
Tue Jun 21 22:57:05 2016 - [info] Alive Servers:
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.20(192.168.1.20:3306)
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.40(192.168.1.40:3306)
Tue Jun 21 22:57:05 2016 - [info] Alive Slaves:
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.20(192.168.1.20:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.40(192.168.1.40:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info] Starting GTID based failover.
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] ** Phase 1: Configuration Check Phase completed.
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 2: Dead Master Shutdown Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] Forcing shutdown so that applications never connect to the current master..
Tue Jun 21 22:57:05 2016 - [info] Executing master IP deactivation script:
Tue Jun 21 22:57:05 2016 - [info]   /usr/local/mha/script/master_ip_failover --orig_master_host=192.168.1.30 --orig_master_ip=192.168.1.30 --orig_master_port=3306 --command=stopssh --ssh_us


IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===

Disabling the VIP on old master: 192.168.1.30
Tue Jun 21 22:57:05 2016 - [info]  done.
Tue Jun 21 22:57:05 2016 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Tue Jun 21 22:57:05 2016 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 3: Master Recovery Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] The latest binary log file/position on all slaves is mysql-bin.000002:373
Tue Jun 21 22:57:05 2016 - [info] Latest slaves (Slaves that received relay log files to the latest):
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.20(192.168.1.20:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.40(192.168.1.40:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info] The oldest binary log file/position on all slaves is mysql-bin.000002:373
Tue Jun 21 22:57:05 2016 - [info] Oldest slaves:
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.20(192.168.1.20:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.40(192.168.1.40:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 3.3: Determining New Master Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] Searching new master from slaves..
Tue Jun 21 22:57:05 2016 - [info]  Candidate masters from the configuration file:
Tue Jun 21 22:57:05 2016 - [info]   192.168.1.20(192.168.1.20:3306)  Version=5.6.31-log (oldest major version between slaves) log-bin:enabled
Tue Jun 21 22:57:05 2016 - [info]     GTID ON
Tue Jun 21 22:57:05 2016 - [info]     Replicating from 192.168.1.30(192.168.1.30:3306)
Tue Jun 21 22:57:05 2016 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 21 22:57:05 2016 - [info]  Non-candidate masters:
Tue Jun 21 22:57:05 2016 - [info]  Searching from candidate_master slaves which have received the latest relay log events..
Tue Jun 21 22:57:05 2016 - [info] New master is 192.168.1.20(192.168.1.20:3306)
Tue Jun 21 22:57:05 2016 - [info] Starting master failover..
Tue Jun 21 22:57:05 2016 - [info]
From:
192.168.1.30(192.168.1.30:3306) (current master)
 +--192.168.1.20(192.168.1.20:3306)
 +--192.168.1.40(192.168.1.40:3306)

To:
192.168.1.20(192.168.1.20:3306) (new master)
 +--192.168.1.40(192.168.1.40:3306)
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 3.3: New Master Recovery Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info]  Waiting all logs to be applied..
Tue Jun 21 22:57:05 2016 - [info]   done.
Tue Jun 21 22:57:05 2016 - [info] Getting new master's binlog name and position..
Tue Jun 21 22:57:05 2016 - [info]  master-bin.000004:231
Tue Jun 21 22:57:05 2016 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.1.20', MASTER_PORT=3306, MASTER_AUTO_POSIT_USER='slave', MASTER_PASSWORD='xxx';
Tue Jun 21 22:57:05 2016 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: master-bin.000004, 231, 252b2aad-4399-11e6-8ba8-000c29ca702d:2,
4a81183e-3722-11e6-ba60-000c29443328:1-3
Tue Jun 21 22:57:05 2016 - [info] Executing master IP activate script:
Tue Jun 21 22:57:05 2016 - [info]   /usr/local/mha/script/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.1.30 --orig_master_ip=192.168.1.30 --orig_master_portaster_host=192.168.1.20 --new_master_ip=192.168.1.20 --new_master_port=3306 --new_master_user='root' --new_master_password='123'
Unknown option: new_master_user
Unknown option: new_master_password


IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===

Enabling the VIP - 192.168.1.100 on the new master - 192.168.1.20
Tue Jun 21 22:57:05 2016 - [info]  OK.
Tue Jun 21 22:57:05 2016 - [info] ** Finished master recovery successfully.
Tue Jun 21 22:57:05 2016 - [info] * Phase 3: Master Recovery Phase completed.
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 4: Slaves Recovery Phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 4.1: Starting Slaves in parallel..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] -- Slave recovery on host 192.168.1.40(192.168.1.40:3306) started, pid: 37397. Check tmp log /usr/local/mha/192.168.1.40_3306_20160621225704.log if it take
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] Log messages from 192.168.1.40 ...
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info]  Resetting slave 192.168.1.40(192.168.1.40:3306) and starting replication from the new master 192.168.1.20(192.168.1.20:3306)..
Tue Jun 21 22:57:05 2016 - [info]  Executed CHANGE MASTER.
Tue Jun 21 22:57:05 2016 - [info]  Slave started.
Tue Jun 21 22:57:05 2016 - [info]  gtid_wait(252b2aad-4399-11e6-8ba8-000c29ca702d:2,
4a81183e-3722-11e6-ba60-000c29443328:1-3) completed on 192.168.1.40(192.168.1.40:3306). Executed 0 events.
Tue Jun 21 22:57:05 2016 - [info] End of log messages from 192.168.1.40.
Tue Jun 21 22:57:05 2016 - [info] -- Slave on host 192.168.1.40(192.168.1.40:3306) started.
Tue Jun 21 22:57:05 2016 - [info] All new slave servers recovered successfully.
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] * Phase 5: New master cleanup phase..
Tue Jun 21 22:57:05 2016 - [info]
Tue Jun 21 22:57:05 2016 - [info] Resetting slave info on the new master..
Tue Jun 21 22:57:05 2016 - [info]  192.168.1.20: Resetting slave info succeeded.
Tue Jun 21 22:57:05 2016 - [info] Master failover to 192.168.1.20(192.168.1.20:3306) completed successfully.
Tue Jun 21 22:57:05 2016 - [info] Deleted server2 entry from /etc/mha/mha.conf .
Tue Jun 21 22:57:05 2016 - [info]

----- Failover Report -----

mha: MySQL Master failover 192.168.1.30(192.168.1.30:3306) to 192.168.1.20(192.168.1.20:3306) succeeded

Master 192.168.1.30(192.168.1.30:3306) is down!

Check MHA Manager logs at db-one for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 192.168.1.30(192.168.1.30:3306)
Selected 192.168.1.20(192.168.1.20:3306) as a new master.
192.168.1.20(192.168.1.20:3306): OK: Applying all logs succeeded.
192.168.1.20(192.168.1.20:3306): OK: Activated master IP address.
192.168.1.40(192.168.1.40:3306): OK: Slave started, replicating from 192.168.1.20(192.168.1.20:3306)
192.168.1.20(192.168.1.20:3306): Resetting slave info succeeded.
Master failover to 192.168.1.20(192.168.1.20:3306) completed successfully.
Tue Jun 21 22:57:05 2016 - [info] Sending mail..

（over）

记录Python学习
关注
专栏目录
MHA + keepalived
小雷音寺
12-05 1121
1.keepalived 原理：通过VRRP协议来保证高可用性 VRRP是一种容错协议，它通过把几台路由设备联合组成一台虚拟的路由设备，并通过一定的机制来保证当主机的下一跳设备出现故障时，可以及时将业务切换到其它设备，从而保持通讯的连续性和可靠性。 VRRP将局域网内的一组路由器划分在一起，称为一个备份组。备份组由一个Master路由器和多个Backup路由器组成，功能上相当于一台虚拟路由器。局域...
MySQL MHA+Keepalived
yiyuf的专栏
10-21 4528
一、MHA的简单介绍 MHA是由perl语言编写的,用外挂脚本的方式实现mysql主从复制的高可用性。 MHA可以自动检测mysql是否宕机,如果宕机,在10-30s内完成new master的选举,应用所有差异的binlog日志到所有slave,将所有的slave切换到新的master上来。 MHA除了自动检测mysql是否宕机,还能够交互式的切换master,在日常的数据库维护中,这个功
MHA+keepalived
wana_one_gy的博客
10-07 1276
MHA介绍： 作为MySQL高可用性环境下故障切换和主从提升的高可用软件，MySQL故障切换过程中，MHA能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数据的一致性，以达到真正意义上的高可用。该软件由两部分组成：MHA Manager（管理节点）和MHA Node（数据节点）。MHA Manager可以部署在任何一台从服务器上或者独立的...
mysql mha+keepalived
wll的专栏
03-25 990
1、 三台机器配置互信关系 ssh-keygen -t dsa ssh-keygen -t rsa 2、 配置hosts文件 Vi /etc/hosts 10.10.6.86   dg 10.10.6.87   dg2 10.10.6.90   dgt 3、搭建主从从 dg--->dg2--->dgt 主(node)   从(node)    从(mange)
mysql mha keepalived_MHA+keepalived 高可用MYSQL集群(续)
weixin_31458459的博客
01-19 764
一、恢复背景二、修复故障节点及MHA集群三、提升已修复的节点为master四、注意事项一、恢复背景1、设备清单2、：percona-xtrabackup-2.3.2(注：生产环境应定时备份；不应等到数据库DOWN后才备份，以免加剧集群的压力)备份数据库操作：[root@jev72 ~]#innobackupex --user=root --password=centos /data/。 。 。xt...
lvs+keepalived+mha+mysql架构配置说明
08-30
lvs+keepalived+mha+mysql 架构配置说明 LVS（Linux Virtual Server）是一种开源的负载均衡解决方案，旨在提高服务器集群的可用性和可扩展性。在高可用架构中，LVS 通常与 Keepalived 配合使用，以提供高可用的负载...
lvs+keepalived+mha+mysql架构最佳部署手册
01-09
### lvs+keepalived+mha+mysql高可用架构配置说明 #### 第一部分 MHA介绍 **MHA**（Master High Availability）作为一种成熟的MySQL高可用性解决方案，它由日本开发者Youshimaton创建，旨在为MySQL环境提供故障...
MHA + keepalived mysql高可用方案部署
u011409801的专栏
05-31 816
原理        master出现故障时，可以自动把最新数据的slave提升为新的master，把所有其他的slave重新指向新的master。切换过程对应用程序透明。迁移时间20-30秒左右。        自动切换过程中，mha尝试从原master保存binlog，最大程度保证数据不丢失，如果服务器宕机（无法ssh连接），mha无法保存二进制日志，只进行故障转移丢失少量最新数据。使用mysq...
mysql+mycat+keepalived+haproxy集群(生产环境实测).doc
08-10
2. 配置Keepalived：在`/etc/keepalived/keepalived.conf`中定义主、备节点的角色，设置监控的检查脚本和VIP。 3. 启动Keepalived：`systemctl start keepalived` 4. 配置VIP漂移：当主节点故障时，VIP会自动漂移到...
MHA+keepalived(补充)
weixin_34318326的博客
11-16 146
MySQL的MHA+keepalived+负载均衡+读写分离架构 MHA只是保证数据库一致性，对于实现应用访问的固定入口、读写分离、负载均衡需要keepalived、中间件、lvs来解决了。 一、如何手动恢复二进制日志， show master logs //查看所有的二进制日志 flush logs;//刷写日志 mysqlbin...
MYSQL高可用集群架构——MHA架构
Parhoia的博客
12-16 1914
MHA高可用集群 文章目录 一、MHA 简介： 二、部署 MHA： 第一步：三台主从服务器安装 mysql 第二步：修改 mysql 的主配置文件：/etc/my.cnf ，注意三台服务器的 server-id 不能一样 第三步：三台服务器启动 mysql 服务 第四步：配置 Mysql 主从同步（一主两从） 第五步：安装 MHA 第六步：启动 MHA 一、MHA 简介： MHA（Master H...
MHA+keepalived集群环境搭建
weixin_30933531的博客
05-19 186
整个MHA+keepalived集群环境搭建 1.1. 环境简介1.1.1、vmvare虚拟机，系统版本CentOS6.5 x86_64位最小化安装，mysql的版本5.7.21，1.1.2、虚拟机器的ssh端口均为默认22,1.1.3、虚拟机的iptables全部关闭，1.1.4、虚拟机的selinux全部关闭，1.1.5、虚拟机服务器时间全部一致 ntpdate 0.asia.pool.nt...
MYSQL高可用架构之MHA实战三 mha+keepalive
wszhm123的博客
09-09 967
MYSQL高可用架构之MHA实战三 mha+keepalive
MHA+keepalived实现Mysql高可用及读写分离
CC的博客
01-10 776
1.准备工作 1.准备机器（5台） keepalived+mha（2台）： 10.11.13.11 keepalived master及mha管理机公用 10.11.13.12 keepalived slave 10.11.13.241 keepalived vip 10.11.13.242 mha vip mysql（3台）： 10.11.13.13 mast...
MHA0.58+Keepalived部署文档
雪辉博客
03-04 820
文章目录一、基础环境配置1.1 关闭防火墙和selinux1.1.1 关闭防火墙1.1.2 关闭selinux1.2 配置IP域名映射1.3 设置swap分区大小1.4 操作系统限制1.5 关闭numa1.6 配置互信二、实例安装2.1 创建MySQL用户组和用户2.2 创建相关目录2.3 解压安装包并设置权限2.4 软链接程序目录并配置环境变量2.5 修改配置文件2.6 初始化数据库2.7 启动数据库服务2.8 搭建复制三、搭建MHA3.1 Ansible 配置(可选)3.2 MHA node安装3.3
MHA+keepalive高可用环境搭建
雅冰石的专栏
02-17 6828
MHA（Master HighAvailability）目前在MySQL高可用方面是一个相对成熟的解决方案，它由日本DeNA公司youshimaton（现就职于Facebook公司）开发，是一套优秀的作为MySQL高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数...
mysql mha keepalived_MySQL之MHA+keepalived方案演示(四)
weixin_39722025的博客
01-19 802
配置VIP实现MHA架构中主库故障自动切换1.说明引入keepalived实现MHA架构中主库master故障时，从库slave自动提升为新的maservip配置可以采用两种方式:一种通过keepalived的方式管理虚拟ip的浮动；另外一种通过脚本方式启动虚拟ip的方式(即不需要keepalived或者heartbeat类似的软件)。此处先介绍通过安装keepalived来管理虚拟IP的浮动：1...
Keepalived+Mha半同步复制实现高可用
weixin_40368523的博客
01-29 478
Mha+Keepalived高可用搭建 MHA工作原理 从宕机崩溃的Master保存二进制日志事件（binlog event）； 识别含有最新更新的Slave； 应用差异的中继日志（relay log）到其他Slave； 应用从Master保存的二进制日志事件； 提升一个Slave为新的Master； 使其他的Slave连接新的Master进行复制； 在MySQL故障切换过程中，MHA能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数据的一致性，以达
整个MHA+keepalived集群环境搭建
guoshaoliang789的专栏
01-08 1537
整个MHA+keepalived集群环境搭建 1.1. 环境简介 1.1.1、vmvare虚拟机，系统版本CentOS6.5 x86_64位最小化安装，mysql的版本5.7.21， 1.1.2、虚拟机器的ssh端口均为默认22, 1.1.3、虚拟机的iptables全部关闭， 1.1.4、虚拟机的selinux全部关闭， 1.1.5、虚拟机服务器时间全部一致 ntpdate 0.asia.p...
MHA+LVS+Keepalived+MySQL高可用架构配置详解
"lvs+keepalived+mha+mysql高可用架构配置说明" 本文档详细阐述了一种基于lvs+keepalived+mha+mysql的高可用架构配置方法，旨在提供一套稳定、高效的数据库集群解决方案。该架构的核心是通过MHA（Master High ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值