CentOS6.8下MySQL MHA架构搭建笔记

最新推荐文章于 2024-07-29 22:40:28 发布
最新推荐文章于 2024-07-29 22:40:28 发布
阅读量133 收藏
点赞数
文章标签： 数据库 运维 操作系统
原文链接：http://www.cnblogs.com/ajiangg/p/6552855.html
版权

转载请注明出处，本文地址：http://www.cnblogs.com/ajiangg/p/6552855.html 

以下是CentOS6.8下MySQL MHA架构搭建笔记

IP资源规划：

192.168.206.139 master

192.168.206.140 slave01(备用master)

192.168.206.141 slave02

192.168.206.142 manager

192.168.206.145 VIP

一、准备工作：

1.关闭Selinux

[root@localhost ~]# vi /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#     enforcing - SELinux security policy is enforced.
#     permissive - SELinux prints warnings instead of enforcing.
#     disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
#     targeted - Targeted processes are protected,
#     mls - Multi Level Security protection.
SELINUXTYPE=targeted
View Code 
[root@localhost ~]# reboot

2.关闭防火墙

[root@localhost ~]# chkconfig iptables off
[root@localhost ~]# service iptables stop

3.安装epel yum源

[root@localhost tmp]# rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
[root@localhost tmp]# rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6

4.安装MHA node所需的perl模块（DBD:mysql）

[root@localhost tmp]# yum -y install perl-DBD-MySQL ncftp perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Time-HiRes perl-devel

二、Replication搭建

1.建立replication用户(master和slave01)

mysql> GRANT REPLICATION SLAVE ON *.* TO 'u_repl'@'192.168.206.%' IDENTIFIED BY 'replpass' with grant option;

2.建立MHA管理用用户

mysql> GRANT ALL PRIVILEGES ON *.* to 'root'@'192.168.206.%' IDENTIFIED BY 'checkpass';

3.安装半同步复制插件

mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';

4.修改my.cnf配置文件

[root@localhost tmp]# vi /etc/my.cnf
# For advice on how to change settings please see
# http://dev.mysql.com/doc/refman/5.7/en/server-configuration-defaults.html

[mysqld]
#
# Remove leading # and set to the amount of RAM for the most important data
# cache in MySQL. Start at 70% of total RAM for dedicated server, else 10%.
# innodb_buffer_pool_size = 128M
#
# Remove leading # to turn on a very important data integrity option: logging
# changes to the binary log between backups.
# log_bin
#
# Remove leading # to set options mainly useful for reporting servers.
# The server defaults are faster for transactions and fast SELECTs.
# Adjust sizes as needed, experiment to find the optimal values.
# join_buffer_size = 128M
# sort_buffer_size = 2M
# read_rnd_buffer_size = 2M
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
server_id=139
log_bin=/var/lib/mysql/mysql-bin
binlog-format=ROW
binlog-checksum=CRC32
log_slave_updates=true
gtid-mode=on
enforce-gtid-consistency=true
master_info_repository=TABLE
sync-master-info=1
slave-parallel-workers=2
master-verify-checksum=1
slave-sql-verify-checksum=1
relay_log=/var/lib/mysql/localhost-relay-bin
relay_log_purge=0
relay_log_recovery=1
rpl_semi_sync_master_enabled=ON
rpl_semi_sync_slave_enabled=ON

# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
View Code

5.master备份slave还原（略），查找master Binlog位置

[root@localhost tmp]# mysql -uroot -p
mysql> show master status\G;
*************************** 1. row ***************************
             File: mysql-bin.000001
         Position: 154
     Binlog_Do_DB: 
 Binlog_Ignore_DB: 
Executed_Gtid_Set: 
1 row in set (0.00 sec)
View Code

6.各slave上执行脚本，建立主从配置。(MySQL5.7可以直接使用master_auto_position=1参数)

mysql> change master to master_host='192.168.206.139',master_user='u_repl',master_password='replpass',master_log_file='mysql-bin.000001' ,master_log_pos=154;
mysql> start slave;

三、开始安装配置

1.各节点使用ssh-keygen实现三台机器之间相互免密钥登录

Memo:如果是直接通过修改/root/.ssh/authorized_keys，需要在安装manager的服务器上把自己的key也加进去，否则masterha_check_ssh验证通不过。

[root@localhost tmp]# ssh-keygen -t rsa
[root@localhost tmp]# ssh-keygen -t rsa
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:
d5:0d:37:75:67:54:47:f0:e4:72:34:26:29:0d:1b:ba root@localhost.localdomain
The key's randomart image is:
+--[ RSA 2048]----+
|           o+.=B&|
|          .oo*oB=|
|         ...o o +|
|         ..    o |
|        SE       |
|                 |
|                 |
|                 |
|                 |
+-----------------+
View Code 
[root@localhost .ssh]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.206.140
[root@localhost .ssh]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.206.140
root@192.168.206.140's password: 
Now try logging into the machine, with "ssh 'root@192.168.206.140'", and check in:

  .ssh/authorized_keys

to make sure we haven't added extra keys that you weren't expecting.
View Code 
[root@localhost .ssh]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.206.141
[root@localhost .ssh]# ssh-copy-id -i /root/.ssh/id_rsa.pub root@192.168.206.142

2.所有节点(包括manager)下载安装mha4mysql-node-0.56

由于google被墙，我是直接从网上下载的rpm文件，具体下载过程略。

[root@localhost tmp]# yum localinstall mha4mysql-node-0.56-0.el6.noarch.rpm
[root@localhost tmp]# yum localinstall mha4mysql-node-0.56-0.el6.noarch.rpm
Loaded plugins: fastestmirror, refresh-packagekit, security
Setting up Local Package Process
Examining mha4mysql-node-0.56-0.el6.noarch.rpm: mha4mysql-node-0.56-0.el6.noarch
Marking mha4mysql-node-0.56-0.el6.noarch.rpm to be installed
Loading mirror speeds from cached hostfile
 * base: ftp.sjtu.edu.cn
 * epel: mirrors.tuna.tsinghua.edu.cn
 * extras: centos.ustc.edu.cn
 * updates: ftp.sjtu.edu.cn
Resolving Dependencies
--> Running transaction check
---> Package mha4mysql-node.noarch 0:0.56-0.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================================================
 Package                                     Arch                                Version                                 Repository                                                      Size
==============================================================================================================================================================================================
Installing:
 mha4mysql-node                              noarch                              0.56-0.el6                              /mha4mysql-node-0.56-0.el6.noarch                              102 k

Transaction Summary
==============================================================================================================================================================================================
Install       1 Package(s)

Total size: 102 k
Installed size: 102 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : mha4mysql-node-0.56-0.el6.noarch                                                                                                                                           1/1 
  Verifying  : mha4mysql-node-0.56-0.el6.noarch                                                                                                                                           1/1 

Installed:
  mha4mysql-node.noarch 0:0.56-0.el6                                                                                                                                                          

Complete!
View Code

确认安装内容

[root@localhost tmp]# rpm -ql mha4mysql-node
[root@localhost tmp]# rpm -ql mha4mysql-node
/usr/bin/apply_diff_relay_logs
/usr/bin/filter_mysqlbinlog
/usr/bin/purge_relay_logs
/usr/bin/save_binary_logs
/usr/share/man/man1/apply_diff_relay_logs.1.gz
/usr/share/man/man1/filter_mysqlbinlog.1.gz
/usr/share/man/man1/purge_relay_logs.1.gz
/usr/share/man/man1/save_binary_logs.1.gz
/usr/share/perl5/vendor_perl/MHA/BinlogHeaderParser.pm
/usr/share/perl5/vendor_perl/MHA/BinlogManager.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFindManager.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinder.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinderElp.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinderXid.pm
/usr/share/perl5/vendor_perl/MHA/NodeConst.pm
/usr/share/perl5/vendor_perl/MHA/NodeUtil.pm
/usr/share/perl5/vendor_perl/MHA/SlaveUtil.pm
View Code
3.manager节点安装mha4mysql-manager-0.56
[root@localhost tmp]# yum localinstall mha4mysql-manager-0.56-0.el6.noarch.rpm
[root@localhost tmp]# yum localinstall mha4mysql-manager-0.56-0.el6.noarch.rpm
Loaded plugins: fastestmirror, refresh-packagekit, security
Setting up Local Package Process
Examining mha4mysql-manager-0.56-0.el6.noarch.rpm: mha4mysql-manager-0.56-0.el6.noarch
Marking mha4mysql-manager-0.56-0.el6.noarch.rpm to be installed
Loading mirror speeds from cached hostfile
 * base: mirrors.163.com
 * epel: mirror01.idc.hinet.net
 * extras: mirrors.cn99.com
 * updates: mirrors.cn99.com
Resolving Dependencies
--> Running transaction check
---> Package mha4mysql-manager.noarch 0:0.56-0.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

==============================================================================================================================================================================================
 Package                                      Arch                              Version                                 Repository                                                       Size
==============================================================================================================================================================================================
Installing:
 mha4mysql-manager                            noarch                            0.56-0.el6                              /mha4mysql-manager-0.56-0.el6.noarch                            325 k

Transaction Summary
==============================================================================================================================================================================================
Install       1 Package(s)

Total size: 325 k
Installed size: 325 k
Is this ok [y/N]: y
Downloading Packages:
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : mha4mysql-manager-0.56-0.el6.noarch                                                                                                                                        1/1 
  Verifying  : mha4mysql-manager-0.56-0.el6.noarch                                                                                                                                        1/1 

Installed:
  mha4mysql-manager.noarch 0:0.56-0.el6                                                                                                                                                       

Complete!
View Code

确认安装内容

[root@localhost tmp]# rpm -ql mha4mysql-manager
[root@localhost tmp]# rpm -ql mha4mysql-node
/usr/bin/apply_diff_relay_logs
/usr/bin/filter_mysqlbinlog
/usr/bin/purge_relay_logs
/usr/bin/save_binary_logs
/usr/share/man/man1/apply_diff_relay_logs.1.gz
/usr/share/man/man1/filter_mysqlbinlog.1.gz
/usr/share/man/man1/purge_relay_logs.1.gz
/usr/share/man/man1/save_binary_logs.1.gz
/usr/share/perl5/vendor_perl/MHA/BinlogHeaderParser.pm
/usr/share/perl5/vendor_perl/MHA/BinlogManager.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFindManager.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinder.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinderElp.pm
/usr/share/perl5/vendor_perl/MHA/BinlogPosFinderXid.pm
/usr/share/perl5/vendor_perl/MHA/NodeConst.pm
/usr/share/perl5/vendor_perl/MHA/NodeUtil.pm
/usr/share/perl5/vendor_perl/MHA/SlaveUtil.pm
[root@localhost tmp]# rpm -ql mha4mysql-manager
/usr/bin/masterha_check_repl
/usr/bin/masterha_check_ssh
/usr/bin/masterha_check_status
/usr/bin/masterha_conf_host
/usr/bin/masterha_manager
/usr/bin/masterha_master_monitor
/usr/bin/masterha_master_switch
/usr/bin/masterha_secondary_check
/usr/bin/masterha_stop
/usr/share/man/man1/masterha_check_repl.1.gz
/usr/share/man/man1/masterha_check_ssh.1.gz
/usr/share/man/man1/masterha_check_status.1.gz
/usr/share/man/man1/masterha_conf_host.1.gz
/usr/share/man/man1/masterha_manager.1.gz
/usr/share/man/man1/masterha_master_monitor.1.gz
/usr/share/man/man1/masterha_master_switch.1.gz
/usr/share/man/man1/masterha_secondary_check.1.gz
/usr/share/man/man1/masterha_stop.1.gz
/usr/share/perl5/vendor_perl/MHA/Config.pm
/usr/share/perl5/vendor_perl/MHA/DBHelper.pm
/usr/share/perl5/vendor_perl/MHA/FileStatus.pm
/usr/share/perl5/vendor_perl/MHA/HealthCheck.pm
/usr/share/perl5/vendor_perl/MHA/ManagerAdmin.pm
/usr/share/perl5/vendor_perl/MHA/ManagerAdminWrapper.pm
/usr/share/perl5/vendor_perl/MHA/ManagerConst.pm
/usr/share/perl5/vendor_perl/MHA/ManagerUtil.pm
/usr/share/perl5/vendor_perl/MHA/MasterFailover.pm
/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm
/usr/share/perl5/vendor_perl/MHA/MasterRotate.pm
/usr/share/perl5/vendor_perl/MHA/SSHCheck.pm
/usr/share/perl5/vendor_perl/MHA/Server.pm
/usr/share/perl5/vendor_perl/MHA/ServerManager.pm
View Code
4.在manager节点管理MHA配置文件

前面采用yum安装的，没有samples文件夹，所以另外down了一份mha4mysql-manager-0.56.tar.gz包（具体过程略）

[root@localhost tmp]# tar xf mha4mysql-manager-0.56.tar.gz
[root@localhost tmp]# cd mha4mysql-manager-0.56
[root@localhost mha4mysql-manager-0.56]# mkdir -p /etc/mha/{app1,scripts}
[root@localhost mha4mysql-manager-0.56]# cp -r samples/conf/* /etc/mha/
[root@localhost mha4mysql-manager-0.56]# cp -r samples/scripts/* /etc/mha/scripts/
[root@localhost mha4mysql-manager-0.56]# mv /etc/mha/app1.cnf /etc/mha/app1/
[root@localhost mha4mysql-manager-0.56]# mv /etc/mha/masterha_default.cnf /etc/masterha_default.cnf

5.在manager上设置全局配置

修改master_ip_failover脚本，添加VIP漂移相关三个参数

[root@localhost mha4mysql-manager-0.56]# vi /etc/mha/scripts/master_ip_failover
[root@localhost scripts]# vi master_ip_failover

#!/usr/bin/env perl

#  Copyright (C) 2011 DeNA Co.,Ltd.
#
#  This program is free software; you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  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,
  $virtual_ip,     $orig_master_vip_eth,  $new_master_vip_eth
);
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,
  'virtual_ip=s'          => \$virtual_ip,
  'orig_master_vip_eth=s' => \$orig_master_vip_eth,
  'new_master_vip_eth=s'  => \$new_master_vip_eth
);

exit &main();

sub main {
  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 {

      # updating global catalog, etc
      `ssh $orig_master_host -o "ConnectTimeout=5" '/sbin/ifconfig $orig_master_vip_eth down'`;
      $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 {
      my $new_master_handler = new MHA::DBHelper();

      # args: hostname, port, user, password, raise_error_or_not
      $new_master_handler->connect( $new_master_ip, $new_master_port,
        $new_master_user, $new_master_password, 1 );

      ## Set read_only=0 on the new master
      $new_master_handler->disable_log_bin_local();
      print "Set read_only=0 on the new master.\n";
      $new_master_handler->disable_read_only();

      ## Creating an app user on the new master
      print "Creating app user on the new master..\n";
      # FIXME_xxx_create_user( $new_master_handler->{dbh} );
      $new_master_handler->enable_log_bin_local();
      $new_master_handler->disconnect();

      ## Update master ip on the catalog database, etc
      # FIXME_xxx;

      my $real_eth=$new_master_vip_eth;
      $real_eth=~ s/:.*//g;
      my $new_master_network= `ssh $new_master_host '/sbin/ifconfig $real_eth'`;
      my $vip_netmask = join(".", $new_master_network =~ /Mask\:(\d+)\.(\d+)\.(\d+)\.(\d+)/ );
      my $vip_broadcast = join(".", $new_master_network =~ /Bcast\:(\d+)\.(\d+)\.(\d+)\.(\d+)/ );
      `ssh $new_master_host -o "ConnectTimeout=15" '/sbin/ifconfig $new_master_vip_eth $virtual_ip netmask $vip_netmask up; /sbin/arping -c 3 -A $virtual_ip; ping -I $virtual_ip -b $vip_broadcast -c 3 -c 3 -i 0.01 -q -W 10 > /dev/null'`;

      $exit_code = 0;
    };
    if ($@) {
      warn $@;

      # If you want to continue failover, exit 10.
      exit $exit_code;
    }
    exit $exit_code;
  }
  elsif ( $command eq "status" ) {

    # do nothing
    exit 0;
  }
  else {
    &usage();
    exit 1;
  }
}

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 --virtual_ip=ip --orig_master_vip_eth=eth --new_master_vip_eth=eth\n";
}
View Code

修改master_ip_online_change脚本，添加VIP漂移相关三个参数

[root@localhost scripts]# vi master_ip_online_change
[root@localhost scripts]# vi master_ip_online_change

#!/usr/bin/env perl

#  Copyright (C) 2011 DeNA Co.,Ltd.
#
#  This program is free software; you can redistribute it and/or modify
#  it under the terms of the GNU General Public License as published by
#  the Free Software Foundation; either version 2 of the License, or
#  (at your option) any later version.
#
#  This program is distributed in the hope that it will be useful,
#  but WITHOUT ANY WARRANTY; without even the implied warranty of
#  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#  GNU General Public License for more details.
#
#  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;
use MHA::NodeUtil;
use Time::HiRes qw( sleep gettimeofday tv_interval );
use Data::Dumper;

my $_tstart;
my $_running_interval = 0.1;
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,
  $virtual_ip,     $orig_master_vip_eth,  $new_master_vip_eth
);
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,
  'virtual_ip=s'          => \$virtual_ip,
  'orig_master_vip_eth=s' => \$orig_master_vip_eth,
  'new_master_vip_eth=s'  => \$new_master_vip_eth
);

exit &main();

sub current_time_us {
  my ( $sec, $microsec ) = gettimeofday();
  my $curdate = localtime($sec);
  return $curdate . " " . sprintf( "%06d", $microsec );
}

sub sleep_until {
  my $elapsed = tv_interval($_tstart);
  if ( $_running_interval > $elapsed ) {
    sleep( $_running_interval - $elapsed );
  }
}

sub get_threads_util {
  my $dbh                    = shift;
  my $my_connection_id       = shift;
  my $running_time_threshold = shift;
  my $type                   = shift;
  $running_time_threshold = 0 unless ($running_time_threshold);
  $type                   = 0 unless ($type);
  my @threads;

  my $sth = $dbh->prepare("SHOW PROCESSLIST");
  $sth->execute();

  while ( my $ref = $sth->fetchrow_hashref() ) {
    my $id         = $ref->{Id};
    my $user       = $ref->{User};
    my $host       = $ref->{Host};
    my $command    = $ref->{Command};
    my $state      = $ref->{State};
    my $query_time = $ref->{Time};
    my $info       = $ref->{Info};
    $info =~ s/^\s*(.*?)\s*$/$1/ if defined($info);
    next if ( $my_connection_id == $id );
    next if ( defined($query_time) && $query_time < $running_time_threshold );
    next if ( defined($command)    && $command eq "Binlog Dump" );
    next if ( defined($user)       && $user eq "system user" );
    next
      if ( defined($command)
      && $command eq "Sleep"
      && defined($query_time)
      && $query_time >= 1 );

    if ( $type >= 1 ) {
      next if ( defined($command) && $command eq "Sleep" );
      next if ( defined($command) && $command eq "Connect" );
    }

    if ( $type >= 2 ) {
      next if ( defined($info) && $info =~ m/^select/i );
      next if ( defined($info) && $info =~ m/^show/i );
    }

    push @threads, $ref;
  }
  return @threads;
}

sub main {
  if ( $command eq "stop" ) {
    ## Gracefully killing connections on the current master
    # 1. Set read_only= 1 on the new master
    # 2. DROP USER so that no app user can establish new connections
    # 3. Set read_only= 1 on the current master
    # 4. Kill current queries
    # * Any database access failure will result in script die.
    my $exit_code = 1;
    eval {
      ## Setting read_only=1 on the new master (to avoid accident)
      my $new_master_handler = new MHA::DBHelper();

      # args: hostname, port, user, password, raise_error(die_on_error)_or_not
      $new_master_handler->connect( $new_master_ip, $new_master_port,
        $new_master_user, $new_master_password, 1 );
      print current_time_us() . " Set read_only on the new master.. ";
      $new_master_handler->enable_read_only();
      if ( $new_master_handler->is_read_only() ) {
        print "ok.\n";
      }
      else {
        die "Failed!\n";
      }
      $new_master_handler->disconnect();

      # Connecting to the orig master, die if any database error happens
      my $orig_master_handler = new MHA::DBHelper();
      $orig_master_handler->connect( $orig_master_ip, $orig_master_port,
        $orig_master_user, $orig_master_password, 1 );

      ## Drop application user so that nobody can connect. Disabling per-session binlog beforehand
      $orig_master_handler->disable_log_bin_local();
      print current_time_us() . " Drpping app user on the orig master..\n";
      # FIXME_xxx_drop_app_user($orig_master_handler);

      ## Waiting for N * 100 milliseconds so that current connections can exit
      my $time_until_read_only = 15;
      $_tstart = [gettimeofday];
      my @threads = get_threads_util( $orig_master_handler->{dbh},
        $orig_master_handler->{connection_id} );
      while ( $time_until_read_only > 0 && $#threads >= 0 ) {
        if ( $time_until_read_only % 5 == 0 ) {
          printf
"%s Waiting all running %d threads are disconnected.. (max %d milliseconds)\n",
            current_time_us(), $#threads + 1, $time_until_read_only * 100;
          if ( $#threads < 5 ) {
            print Data::Dumper->new( [$_] )->Indent(0)->Terse(1)->Dump . "\n"
              foreach (@threads);
          }
        }
        sleep_until();
        $_tstart = [gettimeofday];
        $time_until_read_only--;
        @threads = get_threads_util( $orig_master_handler->{dbh},
          $orig_master_handler->{connection_id} );
      }

      ## Setting read_only=1 on the current master so that nobody(except SUPER) can write
      print current_time_us() . " Set read_only=1 on the orig master.. ";
      $orig_master_handler->enable_read_only();
      if ( $orig_master_handler->is_read_only() ) {
        print "ok.\n";
      }
      else {
        die "Failed!\n";
      }

      ## Waiting for M * 100 milliseconds so that current update queries can complete
      my $time_until_kill_threads = 5;
      @threads = get_threads_util( $orig_master_handler->{dbh},
        $orig_master_handler->{connection_id} );
      while ( $time_until_kill_threads > 0 && $#threads >= 0 ) {
        if ( $time_until_kill_threads % 5 == 0 ) {
          printf
"%s Waiting all running %d queries are disconnected.. (max %d milliseconds)\n",
            current_time_us(), $#threads + 1, $time_until_kill_threads * 100;
          if ( $#threads < 5 ) {
            print Data::Dumper->new( [$_] )->Indent(0)->Terse(1)->Dump . "\n"
              foreach (@threads);
          }
        }
        sleep_until();
        $_tstart = [gettimeofday];
        $time_until_kill_threads--;
        @threads = get_threads_util( $orig_master_handler->{dbh},
          $orig_master_handler->{connection_id} );
      }

      ## Terminating all threads
      print current_time_us() . " Killing all application threads..\n";
      $orig_master_handler->kill_threads(@threads) if ( $#threads >= 0 );
      print current_time_us() . " done.\n";
      $orig_master_handler->enable_log_bin_local();
      $orig_master_handler->disconnect();

      ## After finishing the script, MHA executes FLUSH TABLES WITH READ LOCK
      $exit_code = 0;
    };
    if ($@) {
      warn "Got Error: $@\n";
      exit $exit_code;
    }
    exit $exit_code;
  }
  elsif ( $command eq "start" ) {
    ## Activating master ip on the new master
    # 1. Create app user with write privileges
    # 2. Moving backup script if needed
    # 3. Register new master's ip to the catalog database

# We don't return error even though activating updatable accounts/ip failed so that we don't interrupt slaves' recovery.
# If exit code is 0 or 10, MHA does not abort
    my $exit_code = 10;
    eval {
      my $new_master_handler = new MHA::DBHelper();

      # args: hostname, port, user, password, raise_error_or_not
      $new_master_handler->connect( $new_master_ip, $new_master_port,
        $new_master_user, $new_master_password, 1 );

      ## Set read_only=0 on the new master
      $new_master_handler->disable_log_bin_local();
      print current_time_us() . " Set read_only=0 on the new master.\n";
      $new_master_handler->disable_read_only();

      ## Creating an app user on the new master
      print current_time_us() . " Creating app user on the new master..\n";
      # FIXME_xxx_create_app_user($new_master_handler);
      $new_master_handler->enable_log_bin_local();
      $new_master_handler->disconnect();

      ## Update master ip on the catalog database, etc
      `ssh $orig_master_host -o "ConnectTimeout=5" '/sbin/ifconfig $orig_master_vip_eth down'`;
      my $real_eth=$new_master_vip_eth;
      $real_eth=~ s/:.*//g;
      my $new_master_network= `ssh $new_master_host '/sbin/ifconfig $real_eth'`;
      my $vip_netmask = join(".", $new_master_network =~ /Mask\:(\d+)\.(\d+)\.(\d+)\.(\d+)/ );
      my $vip_broadcast = join(".", $new_master_network =~ /Bcast\:(\d+)\.(\d+)\.(\d+)\.(\d+)/ );
      `ssh $new_master_host -o "ConnectTimeout=15" '/sbin/ifconfig $new_master_vip_eth $virtual_ip netmask $vip_netmask up; /sbin/arping -c 3 -A $virtual_ip; ping -I $virtual_ip -b $vip_broadcast -c 3 -c 3 -i 0.01 -q -W 10 > /dev/null'`;

      $exit_code = 0;
    };
    if ($@) {
      warn "Got Error: $@\n";
      exit $exit_code;
    }
    exit $exit_code;
  }
  elsif ( $command eq "status" ) {

    # do nothing
    exit 0;
  }
  else {
    &usage();
    exit 1;
  }
}

sub usage {
  print
"Usage: master_ip_online_change --command=start|stop|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 --virtual_ip=ip --orig_master_vip_eth=eth --new_master_vip_eth=eth\n";
  die;
}
View Code

修改masterha_default.cnf全局配置

[root@localhost mha4mysql-manager-0.56]# vi /etc/masterha_default.cnf
[root@localhost scripts]# vi /etc/masterha_default.cnf
[server default]
user=root
password=checkpass
ssh_user=root
repl_user=u_repl
repl_password=replpass
master_binlog_dir= /var/lib/mysql,/var/log/mysql
remote_workdir=/data/log/masterha
secondary_check_script= masterha_secondary_check -s 192.168.206.140 -s 192.168.206.139 --user=root --master_host=192.168.206.139 --master_port=3306
ping_interval=3
master_ip_failover_script= /etc/mha/scripts/master_ip_failover --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234
# shutdown_script= /etc/mha/scripts/power_manager
# report_script= /etc/mha/scripts/send_report
master_ip_online_change_script= /etc/mha/scripts/master_ip_online_change --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234
View Code

创建日志目录：

[root@localhost mha4mysql-manager-0.56]# mkdir -p /var/log/mha/app1

配置app1.cnf：

[root@localhost mha4mysql-manager-0.56]# vi /etc/mha/app1/app1.cnf
[root@localhost mha4mysql-manager-0.56]# vi /etc/mha/app1/app1.cnf

[server default]
manager_workdir=/var/log/mha/app1
manager_log=/var/log/mha/app1/manager.log

[server1]
hostname=192.168.206.139
master_binlog_dir=/var/lib/mysql/
candidate_master=1

[server2]
hostname=192.168.206.140
master_binlog_dir=/var/lib/mysql/
candidate_master=1

[server3]
hostname=192.168.206.141
master_binlog_dir=/var/lib/mysql/
no_master=1
View Code

6.验证安装内容

验证ssh信任

[root@localhost mha4mysql-manager-0.56]# masterha_check_ssh --conf=/etc/mha/app1/app1.cnf
[root@localhost mha4mysql-manager-0.56]# masterha_check_ssh --conf=/etc/mha/app1/app1.cnf
Thu Mar 16 03:53:28 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 03:53:28 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 03:53:28 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 03:53:28 2017 - [info] Starting SSH connection tests..
Thu Mar 16 03:53:33 2017 - [debug] 
Thu Mar 16 03:53:28 2017 - [debug]  Connecting via SSH from root@192.168.206.140(192.168.206.140:22) to root@192.168.206.139(192.168.206.139:22)..
Thu Mar 16 03:53:32 2017 - [debug]   ok.
Thu Mar 16 03:53:32 2017 - [debug]  Connecting via SSH from root@192.168.206.140(192.168.206.140:22) to root@192.168.206.141(192.168.206.141:22)..
Thu Mar 16 03:53:33 2017 - [debug]   ok.
Thu Mar 16 03:53:33 2017 - [debug] 
Thu Mar 16 03:53:28 2017 - [debug]  Connecting via SSH from root@192.168.206.139(192.168.206.139:22) to root@192.168.206.140(192.168.206.140:22)..
Thu Mar 16 03:53:32 2017 - [debug]   ok.
Thu Mar 16 03:53:32 2017 - [debug]  Connecting via SSH from root@192.168.206.139(192.168.206.139:22) to root@192.168.206.141(192.168.206.141:22)..
Thu Mar 16 03:53:33 2017 - [debug]   ok.
Thu Mar 16 03:53:33 2017 - [debug] 
Thu Mar 16 03:53:29 2017 - [debug]  Connecting via SSH from root@192.168.206.141(192.168.206.141:22) to root@192.168.206.139(192.168.206.139:22)..
Thu Mar 16 03:53:33 2017 - [debug]   ok.
Thu Mar 16 03:53:33 2017 - [debug]  Connecting via SSH from root@192.168.206.141(192.168.206.141:22) to root@192.168.206.140(192.168.206.140:22)..
Thu Mar 16 03:53:33 2017 - [debug]   ok.
Thu Mar 16 03:53:33 2017 - [info] All SSH connection tests passed successfully.
View Code

验证主从复制

[root@localhost mha4mysql-manager-0.56]# masterha_check_repl --conf=/etc/mha/app1/app1.cnf
[root@localhost mha4mysql-manager-0.56]# masterha_check_repl --conf=/etc/mha/app1/app1.cnf
Thu Mar 16 03:56:02 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 03:56:02 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 03:56:02 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 03:56:02 2017 - [info] MHA::MasterMonitor version 0.56.
Thu Mar 16 03:56:03 2017 - [info] GTID failover mode = 1
Thu Mar 16 03:56:03 2017 - [info] Dead Servers:
Thu Mar 16 03:56:03 2017 - [info] Alive Servers:
Thu Mar 16 03:56:03 2017 - [info]   192.168.206.139(192.168.206.139:3306)
Thu Mar 16 03:56:03 2017 - [info]   192.168.206.140(192.168.206.140:3306)
Thu Mar 16 03:56:03 2017 - [info]   192.168.206.141(192.168.206.141:3306)
Thu Mar 16 03:56:03 2017 - [info] Alive Slaves:
Thu Mar 16 03:56:03 2017 - [info]   192.168.206.140(192.168.206.140:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 03:56:03 2017 - [info]     GTID ON
Thu Mar 16 03:56:03 2017 - [info]     Replicating from 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 03:56:03 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 03:56:03 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 03:56:03 2017 - [info]     GTID ON
Thu Mar 16 03:56:03 2017 - [info]     Replicating from 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 03:56:03 2017 - [info]     Not candidate for the new Master (no_master is set)
Thu Mar 16 03:56:03 2017 - [info] Current Alive Master: 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 03:56:03 2017 - [info] Checking slave configurations..
Thu Mar 16 03:56:03 2017 - [info]  read_only=1 is not set on slave 192.168.206.140(192.168.206.140:3306).
Thu Mar 16 03:56:03 2017 - [info]  read_only=1 is not set on slave 192.168.206.141(192.168.206.141:3306).
Thu Mar 16 03:56:03 2017 - [info] Checking replication filtering settings..
Thu Mar 16 03:56:03 2017 - [info]  binlog_do_db= , binlog_ignore_db= 
Thu Mar 16 03:56:03 2017 - [info]  Replication filtering check ok.
Thu Mar 16 03:56:03 2017 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Thu Mar 16 03:56:03 2017 - [info] Checking SSH publickey authentication settings on the current master..
Thu Mar 16 03:56:08 2017 - [warning] HealthCheck: Got timeout on checking SSH connection to 192.168.206.139! at /usr/share/perl5/vendor_perl/MHA/HealthCheck.pm line 342.
Thu Mar 16 03:56:08 2017 - [info] 
192.168.206.139(192.168.206.139:3306) (current master)
 +--192.168.206.140(192.168.206.140:3306)
 +--192.168.206.141(192.168.206.141:3306)

Thu Mar 16 03:56:08 2017 - [info] Checking replication health on 192.168.206.140..
Thu Mar 16 03:56:08 2017 - [info]  ok.
Thu Mar 16 03:56:08 2017 - [info] Checking replication health on 192.168.206.141..
Thu Mar 16 03:56:08 2017 - [info]  ok.
Thu Mar 16 03:56:08 2017 - [info] Checking master_ip_failover_script status:
Thu Mar 16 03:56:08 2017 - [info]   /etc/mha/scripts/master_ip_failover --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=status --ssh_user=root --orig_master_host=192.168.206.139 --orig_master_ip=192.168.206.139 --orig_master_port=3306 
Thu Mar 16 03:56:08 2017 - [info]  OK.
Thu Mar 16 03:56:08 2017 - [warning] shutdown_script is not defined.
Thu Mar 16 03:56:08 2017 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.
View Code

四、启动MHA、测试MHA故障转移

启动MHA

[root@localhost mha4mysql-manager-0.56]# masterha_manager --conf=/etc/mha/app1/app1.cnf
[root@localhost mha4mysql-manager-0.56]# masterha_manager --conf=/etc/mha/app1/app1.cnf
Thu Mar 16 03:59:39 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 03:59:39 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 03:59:39 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
View Code

或者采用后台启动

[root@localhost mha4mysql-manager-0.56]# nohup masterha_manager --conf=/etc/mha/app1/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/mha/app1/manager.log 2>&1 &
[root@localhost mha4mysql-manager-0.56]# nohup masterha_manager --conf=/etc/mha/app1/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/mha/app1/manager.log 2>&1 &
[3] 5977
[2]   Exit 1                  nohup masterha_manager --conf=/etc/mha/app1/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/mha/app1/manager.log 2>&1
View Code

配置master的VIP

[root@localhost mysql]# /sbin/ifconfig eth0:234 192.168.206.145 netmask 255.255.255.0 up

确认VIP

[root@localhost mysql]# ifconfig
[root@localhost mysql]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0C:29:81:A4:6E  
          inet addr:192.168.206.139  Bcast:192.168.206.255  Mask:255.255.255.0
          inet6 addr: fe80::20c:29ff:fe81:a46e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23074 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11235 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1628296 (1.5 MiB)  TX bytes:1043306 (1018.8 KiB)

eth0:234  Link encap:Ethernet  HWaddr 00:0C:29:81:A4:6E  
          inet addr:192.168.206.145  Bcast:192.168.206.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:240 (240.0 b)  TX bytes:240 (240.0 b)
View Code

确认MHA启动状态：

[root@localhost ~]# masterha_check_status --conf=/etc/mha/app1/app1.cnf
[root@localhost ~]# masterha_check_status --conf=/etc/mha/app1/app1.cnf
app1 (pid:5140) is running(0:PING_OK), master:192.168.206.139
View Code

进程确认：

[root@localhost scripts]# ps aux|grep mha
[root@localhost scripts]# ps aux|grep mha
root       6731  1.8  0.9 194240 18724 pts/1    S    10:16   0:00 perl /usr/bin/masterha_manager --conf=/etc/mha/app1/app1.cnf --remove_dead_master_conf --ignore_last_failover
root       6750  0.0  0.0 103316   844 pts/1    S+   10:16   0:00 grep mha
View Code

关闭MHA Manager监控：

[root@localhost mha4mysql-manager-0.56]# masterha_stop --conf=/etc/mha/app1/app1.cnf
[root@localhost mha4mysql-manager-0.56]# masterha_stop --conf=/etc/mha/app1/app1.cnf
Stopped app1 successfully.
[3]+  Exit 1                  nohup masterha_manager --conf=/etc/mha/app1/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/mha/app1/manager.log 2>&1
View Code

主动切换之交互模式

[root@localhost scripts]# masterha_master_switch --master_state=alive --conf=/etc/mha/app1/app1.cnf --new_master_host=192.168.206.140
[root@localhost scripts]# masterha_master_switch --master_state=alive --conf=/etc/mha/app1/app1.cnf --new_master_host=192.168.206.140
Thu Mar 16 07:57:17 2017 - [info] MHA::MasterRotate version 0.56.
Thu Mar 16 07:57:17 2017 - [info] Starting online master switch..
Thu Mar 16 07:57:17 2017 - [info] 
Thu Mar 16 07:57:17 2017 - [info] * Phase 1: Configuration Check Phase..
Thu Mar 16 07:57:17 2017 - [info] 
Thu Mar 16 07:57:17 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 07:57:17 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 07:57:17 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 07:57:17 2017 - [info] GTID failover mode = 1
Thu Mar 16 07:57:17 2017 - [info] Current Alive Master: 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 07:57:17 2017 - [info] Alive Slaves:
Thu Mar 16 07:57:17 2017 - [info]   192.168.206.140(192.168.206.140:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 07:57:17 2017 - [info]     GTID ON
Thu Mar 16 07:57:17 2017 - [info]     Replicating from 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 07:57:17 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 07:57:17 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 07:57:17 2017 - [info]     GTID ON
Thu Mar 16 07:57:17 2017 - [info]     Replicating from 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 07:57:17 2017 - [info]     Not candidate for the new Master (no_master is set)

It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.206.139(192.168.206.139:3306)? (YES/no): yes
Thu Mar 16 07:57:19 2017 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Thu Mar 16 07:57:19 2017 - [info]  ok.
Thu Mar 16 07:57:19 2017 - [info] Checking MHA is not monitoring or doing failover..
Thu Mar 16 07:57:19 2017 - [info] Checking replication health on 192.168.206.140..
Thu Mar 16 07:57:19 2017 - [info]  ok.
Thu Mar 16 07:57:19 2017 - [info] Checking replication health on 192.168.206.141..
Thu Mar 16 07:57:19 2017 - [info]  ok.
Thu Mar 16 07:57:19 2017 - [info] 192.168.206.140 can be new master.
Thu Mar 16 07:57:19 2017 - [info] 
From:
192.168.206.139(192.168.206.139:3306) (current master)
 +--192.168.206.140(192.168.206.140:3306)
 +--192.168.206.141(192.168.206.141:3306)

To:
192.168.206.140(192.168.206.140:3306) (new master)
 +--192.168.206.141(192.168.206.141:3306)

Starting master switch from 192.168.206.139(192.168.206.139:3306) to 192.168.206.140(192.168.206.140:3306)? (yes/NO): yes
Thu Mar 16 07:57:21 2017 - [info] Checking whether 192.168.206.140(192.168.206.140:3306) is ok for the new master..
Thu Mar 16 07:57:21 2017 - [info]  ok.
Thu Mar 16 07:57:21 2017 - [info] ** Phase 1: Configuration Check Phase completed.
Thu Mar 16 07:57:21 2017 - [info] 
Thu Mar 16 07:57:21 2017 - [info] * Phase 2: Rejecting updates Phase..
Thu Mar 16 07:57:21 2017 - [info] 
Thu Mar 16 07:57:21 2017 - [info] Executing master ip online change script to disable write on the current master:
Thu Mar 16 07:57:21 2017 - [info]   /etc/mha/scripts/master_ip_online_change --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=stop --orig_master_host=192.168.206.139 --orig_master_ip=192.168.206.139 --orig_master_port=3306 --orig_master_user='root' --orig_master_password='replpass' --new_master_host=192.168.206.140 --new_master_ip=192.168.206.140 --new_master_port=3306 --new_master_user='root' --new_master_password='replpass' --orig_master_ssh_user=root --new_master_ssh_user=root  
Thu Mar 16 07:57:21 2017 836071 Set read_only on the new master.. ok.
Thu Mar 16 07:57:21 2017 846572 Drpping app user on the orig master..
Thu Mar 16 07:57:21 2017 848400 Waiting all running 1 threads are disconnected.. (max 1500 milliseconds)
{'Time' => '325','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '58','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:59184'}
Thu Mar 16 07:57:22 2017 350495 Waiting all running 1 threads are disconnected.. (max 1000 milliseconds)
{'Time' => '325','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '58','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:59184'}
Thu Mar 16 07:57:22 2017 853113 Waiting all running 1 threads are disconnected.. (max 500 milliseconds)
{'Time' => '326','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '58','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:59184'}
Thu Mar 16 07:57:23 2017 355738 Set read_only=1 on the orig master.. ok.
Thu Mar 16 07:57:23 2017 360013 Waiting all running 1 queries are disconnected.. (max 500 milliseconds)
{'Time' => '326','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '58','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:59184'}
Thu Mar 16 07:57:23 2017 858184 Killing all application threads..
Thu Mar 16 07:57:23 2017 860278 done.
Thu Mar 16 07:57:23 2017 - [info]  ok.
Thu Mar 16 07:57:23 2017 - [info] Locking all tables on the orig master to reject updates from everybody (including root):
Thu Mar 16 07:57:23 2017 - [info] Executing FLUSH TABLES WITH READ LOCK..
Thu Mar 16 07:57:23 2017 - [info]  ok.
Thu Mar 16 07:57:23 2017 - [info] Orig master binlog:pos is mysql-bin.000003:984.
Thu Mar 16 07:57:23 2017 - [info]  Waiting to execute all relay logs on 192.168.206.140(192.168.206.140:3306)..
Thu Mar 16 07:57:23 2017 - [info]  master_pos_wait(mysql-bin.000003:984) completed on 192.168.206.140(192.168.206.140:3306). Executed 0 events.
Thu Mar 16 07:57:23 2017 - [info]   done.
Thu Mar 16 07:57:23 2017 - [info] Getting new master's binlog name and position..
Thu Mar 16 07:57:23 2017 - [info]  mysql-bin.000002:1033
Thu Mar 16 07:57:23 2017 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.206.140', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='u_repl', MASTER_PASSWORD='xxx';
Thu Mar 16 07:57:23 2017 - [info] Executing master ip online change script to allow write on the new master:
Thu Mar 16 07:57:23 2017 - [info]   /etc/mha/scripts/master_ip_online_change --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=start --orig_master_host=192.168.206.139 --orig_master_ip=192.168.206.139 --orig_master_port=3306 --orig_master_user='root' --orig_master_password='replpass' --new_master_host=192.168.206.140 --new_master_ip=192.168.206.140 --new_master_port=3306 --new_master_user='root' --new_master_password='replpass' --orig_master_ssh_user=root --new_master_ssh_user=root  
Thu Mar 16 07:57:24 2017 094535 Set read_only=0 on the new master.
Thu Mar 16 07:57:24 2017 096832 Creating app user on the new master..
Thu Mar 16 07:57:24 2017 - [info]  ok.
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info] * Switching slaves in parallel..
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info] -- Slave switch on host 192.168.206.141(192.168.206.141:3306) started, pid: 6433
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info] Log messages from 192.168.206.141 ...
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info]  Waiting to execute all relay logs on 192.168.206.141(192.168.206.141:3306)..
Thu Mar 16 07:57:24 2017 - [info]  master_pos_wait(mysql-bin.000003:984) completed on 192.168.206.141(192.168.206.141:3306). Executed 0 events.
Thu Mar 16 07:57:24 2017 - [info]   done.
Thu Mar 16 07:57:24 2017 - [info]  Resetting slave 192.168.206.141(192.168.206.141:3306) and starting replication from the new master 192.168.206.140(192.168.206.140:3306)..
Thu Mar 16 07:57:24 2017 - [info]  Executed CHANGE MASTER.
Thu Mar 16 07:57:24 2017 - [info]  Slave started.
Thu Mar 16 07:57:24 2017 - [info] End of log messages from 192.168.206.141 ...
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info] -- Slave switch on host 192.168.206.141(192.168.206.141:3306) succeeded.
Thu Mar 16 07:57:24 2017 - [info] Unlocking all tables on the orig master:
Thu Mar 16 07:57:24 2017 - [info] Executing UNLOCK TABLES..
Thu Mar 16 07:57:24 2017 - [info]  ok.
Thu Mar 16 07:57:24 2017 - [info] All new slave servers switched successfully.
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info] * Phase 5: New master cleanup phase..
Thu Mar 16 07:57:24 2017 - [info] 
Thu Mar 16 07:57:24 2017 - [info]  192.168.206.140: Resetting slave info succeeded.
Thu Mar 16 07:57:24 2017 - [info] Switching master to 192.168.206.140(192.168.206.140:3306) completed successfully.
View Code

重新将旧的master加入复制，指向新的master

mysql> change master to master_host='192.168.206.140',master_user='u_repl',master_password='replpass',master_auto_position=1;
mysql> start slave;

主动切换之非交互模式：

[root@localhost scripts]# masterha_master_switch --master_state=alive --conf=/etc/mha/app1/app1.cnf --new_master_host=192.168.206.139 --interactive=0
[root@localhost scripts]# masterha_master_switch --master_state=alive --conf=/etc/mha/app1/app1.cnf --new_master_host=192.168.206.139 --interactive=0
Thu Mar 16 07:51:50 2017 - [info] MHA::MasterRotate version 0.56.
Thu Mar 16 07:51:50 2017 - [info] Starting online master switch..
Thu Mar 16 07:51:50 2017 - [info] 
Thu Mar 16 07:51:50 2017 - [info] * Phase 1: Configuration Check Phase..
Thu Mar 16 07:51:50 2017 - [info] 
Thu Mar 16 07:51:50 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 07:51:50 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 07:51:50 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 07:51:50 2017 - [info] GTID failover mode = 1
Thu Mar 16 07:51:50 2017 - [info] Current Alive Master: 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 07:51:50 2017 - [info] Alive Slaves:
Thu Mar 16 07:51:50 2017 - [info]   192.168.206.139(192.168.206.139:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 07:51:50 2017 - [info]     GTID ON
Thu Mar 16 07:51:50 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 07:51:50 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 07:51:50 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 07:51:50 2017 - [info]     GTID ON
Thu Mar 16 07:51:50 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 07:51:50 2017 - [info]     Not candidate for the new Master (no_master is set)
Thu Mar 16 07:51:50 2017 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
Thu Mar 16 07:51:50 2017 - [info]  ok.
Thu Mar 16 07:51:50 2017 - [info] Checking MHA is not monitoring or doing failover..
Thu Mar 16 07:51:50 2017 - [info] Checking replication health on 192.168.206.139..
Thu Mar 16 07:51:50 2017 - [info]  ok.
Thu Mar 16 07:51:50 2017 - [info] Checking replication health on 192.168.206.141..
Thu Mar 16 07:51:50 2017 - [info]  ok.
Thu Mar 16 07:51:50 2017 - [info] 192.168.206.139 can be new master.
Thu Mar 16 07:51:50 2017 - [info] 
From:
192.168.206.140(192.168.206.140:3306) (current master)
 +--192.168.206.139(192.168.206.139:3306)
 +--192.168.206.141(192.168.206.141:3306)

To:
192.168.206.139(192.168.206.139:3306) (new master)
 +--192.168.206.141(192.168.206.141:3306)
Thu Mar 16 07:51:50 2017 - [info] Checking whether 192.168.206.139(192.168.206.139:3306) is ok for the new master..
Thu Mar 16 07:51:50 2017 - [info]  ok.
Thu Mar 16 07:51:50 2017 - [info] ** Phase 1: Configuration Check Phase completed.
Thu Mar 16 07:51:50 2017 - [info] 
Thu Mar 16 07:51:50 2017 - [info] * Phase 2: Rejecting updates Phase..
Thu Mar 16 07:51:50 2017 - [info] 
Thu Mar 16 07:51:50 2017 - [info] Executing master ip online change script to disable write on the current master:
Thu Mar 16 07:51:50 2017 - [info]   /etc/mha/scripts/master_ip_online_change --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=stop --orig_master_host=192.168.206.140 --orig_master_ip=192.168.206.140 --orig_master_port=3306 --orig_master_user='root' --orig_master_password='replpass' --new_master_host=192.168.206.139 --new_master_ip=192.168.206.139 --new_master_port=3306 --new_master_user='root' --new_master_password='replpass' --orig_master_ssh_user=root --new_master_ssh_user=root  
Thu Mar 16 07:51:50 2017 428863 Set read_only on the new master.. ok.
Thu Mar 16 07:51:50 2017 436946 Drpping app user on the orig master..
Thu Mar 16 07:51:50 2017 438015 Waiting all running 1 threads are disconnected.. (max 1500 milliseconds)
{'Time' => '180','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '72','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:48684'}
Thu Mar 16 07:51:50 2017 940921 Waiting all running 1 threads are disconnected.. (max 1000 milliseconds)
{'Time' => '181','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '72','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:48684'}
Thu Mar 16 07:51:51 2017 443500 Waiting all running 1 threads are disconnected.. (max 500 milliseconds)
{'Time' => '181','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '72','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:48684'}
Thu Mar 16 07:51:51 2017 946057 Set read_only=1 on the orig master.. ok.
Thu Mar 16 07:51:51 2017 952395 Waiting all running 1 queries are disconnected.. (max 500 milliseconds)
{'Time' => '182','Command' => 'Binlog Dump GTID','db' => undef,'Id' => '72','Info' => undef,'User' => 'u_repl','State' => 'Master has sent all binlog to slave; waiting for more updates','Host' => '192.168.206.141:48684'}
Thu Mar 16 07:51:52 2017 448683 Killing all application threads..
Thu Mar 16 07:51:52 2017 450864 done.
Thu Mar 16 07:51:52 2017 - [info]  ok.
Thu Mar 16 07:51:52 2017 - [info] Locking all tables on the orig master to reject updates from everybody (including root):
Thu Mar 16 07:51:52 2017 - [info] Executing FLUSH TABLES WITH READ LOCK..
Thu Mar 16 07:51:52 2017 - [info]  ok.
Thu Mar 16 07:51:52 2017 - [info] Orig master binlog:pos is mysql-bin.000002:1033.
Thu Mar 16 07:51:52 2017 - [info]  Waiting to execute all relay logs on 192.168.206.139(192.168.206.139:3306)..
Thu Mar 16 07:51:52 2017 - [info]  master_pos_wait(mysql-bin.000002:1033) completed on 192.168.206.139(192.168.206.139:3306). Executed 0 events.
Thu Mar 16 07:51:52 2017 - [info]   done.
Thu Mar 16 07:51:52 2017 - [info] Getting new master's binlog name and position..
Thu Mar 16 07:51:52 2017 - [info]  mysql-bin.000003:984
Thu Mar 16 07:51:52 2017 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.206.139', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='u_repl', MASTER_PASSWORD='xxx';
Thu Mar 16 07:51:52 2017 - [info] Executing master ip online change script to allow write on the new master:
Thu Mar 16 07:51:52 2017 - [info]   /etc/mha/scripts/master_ip_online_change --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=start --orig_master_host=192.168.206.140 --orig_master_ip=192.168.206.140 --orig_master_port=3306 --orig_master_user='root' --orig_master_password='replpass' --new_master_host=192.168.206.139 --new_master_ip=192.168.206.139 --new_master_port=3306 --new_master_user='root' --new_master_password='replpass' --orig_master_ssh_user=root --new_master_ssh_user=root  
Thu Mar 16 07:51:52 2017 689824 Set read_only=0 on the new master.
Thu Mar 16 07:51:52 2017 691842 Creating app user on the new master..
Thu Mar 16 07:51:56 2017 - [info]  ok.
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info] * Switching slaves in parallel..
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info] -- Slave switch on host 192.168.206.141(192.168.206.141:3306) started, pid: 6405
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info] Log messages from 192.168.206.141 ...
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info]  Waiting to execute all relay logs on 192.168.206.141(192.168.206.141:3306)..
Thu Mar 16 07:51:56 2017 - [info]  master_pos_wait(mysql-bin.000002:1033) completed on 192.168.206.141(192.168.206.141:3306). Executed 0 events.
Thu Mar 16 07:51:56 2017 - [info]   done.
Thu Mar 16 07:51:56 2017 - [info]  Resetting slave 192.168.206.141(192.168.206.141:3306) and starting replication from the new master 192.168.206.139(192.168.206.139:3306)..
Thu Mar 16 07:51:56 2017 - [info]  Executed CHANGE MASTER.
Thu Mar 16 07:51:56 2017 - [info]  Slave started.
Thu Mar 16 07:51:56 2017 - [info] End of log messages from 192.168.206.141 ...
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info] -- Slave switch on host 192.168.206.141(192.168.206.141:3306) succeeded.
Thu Mar 16 07:51:56 2017 - [info] Unlocking all tables on the orig master:
Thu Mar 16 07:51:56 2017 - [info] Executing UNLOCK TABLES..
Thu Mar 16 07:51:56 2017 - [info]  ok.
Thu Mar 16 07:51:56 2017 - [info] All new slave servers switched successfully.
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info] * Phase 5: New master cleanup phase..
Thu Mar 16 07:51:56 2017 - [info] 
Thu Mar 16 07:51:56 2017 - [info]  192.168.206.139: Resetting slave info succeeded.
Thu Mar 16 07:51:56 2017 - [info] Switching master to 192.168.206.139(192.168.206.139:3306) completed successfully.
View Code

Master192.168.206.140宕机模式下切换主从：

masterha_master_switch --master_state=dead --conf=/etc/mha/app1/app1.cnf --dead_master_host=192.168.206.140 --dead_master_ip=192.168.206.140 --dead_master_port=3306 --new_master_host=192.168.206.139
[root@localhost scripts]# masterha_master_switch --master_state=dead --conf=/etc/mha/app1/app1.cnf --dead_master_host=192.168.206.140 --dead_master_ip=192.168.206.140 --dead_master_port=3306 --new_master_host=192.168.206.139
Thu Mar 16 08:09:36 2017 - [info] Reading default configuration from /etc/masterha_default.cnf..
Thu Mar 16 08:09:36 2017 - [info] Reading application default configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 08:09:36 2017 - [info] Reading server configuration from /etc/mha/app1/app1.cnf..
Thu Mar 16 08:09:36 2017 - [info] MHA::MasterFailover version 0.56.
Thu Mar 16 08:09:36 2017 - [info] Starting master failover.
Thu Mar 16 08:09:36 2017 - [info] 
Thu Mar 16 08:09:36 2017 - [info] * Phase 1: Configuration Check Phase..
Thu Mar 16 08:09:36 2017 - [info] 
Thu Mar 16 08:09:37 2017 - [info] GTID failover mode = 1
Thu Mar 16 08:09:37 2017 - [info] Dead Servers:
Thu Mar 16 08:09:37 2017 - [info]   192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:37 2017 - [info] Checking master reachability via MySQL(double check)...
Thu Mar 16 08:09:37 2017 - [info]  ok.
Thu Mar 16 08:09:37 2017 - [info] Alive Servers:
Thu Mar 16 08:09:37 2017 - [info]   192.168.206.139(192.168.206.139:3306)
Thu Mar 16 08:09:37 2017 - [info]   192.168.206.141(192.168.206.141:3306)
Thu Mar 16 08:09:37 2017 - [info] Alive Slaves:
Thu Mar 16 08:09:37 2017 - [info]   192.168.206.139(192.168.206.139:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:37 2017 - [info]     GTID ON
Thu Mar 16 08:09:37 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:37 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 08:09:37 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:37 2017 - [info]     GTID ON
Thu Mar 16 08:09:37 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:37 2017 - [info]     Not candidate for the new Master (no_master is set)
Master 192.168.206.140(192.168.206.140:3306) is dead. Proceed? (yes/NO): yes
Thu Mar 16 08:09:42 2017 - [info] Starting GTID based failover.
Thu Mar 16 08:09:42 2017 - [info] 
Thu Mar 16 08:09:42 2017 - [info] ** Phase 1: Configuration Check Phase completed.
Thu Mar 16 08:09:42 2017 - [info] 
Thu Mar 16 08:09:42 2017 - [info] * Phase 2: Dead Master Shutdown Phase..
Thu Mar 16 08:09:42 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] HealthCheck: SSH to 192.168.206.140 is reachable.
Thu Mar 16 08:09:46 2017 - [info] Forcing shutdown so that applications never connect to the current master..
Thu Mar 16 08:09:46 2017 - [info] Executing master IP deactivation script:
Thu Mar 16 08:09:46 2017 - [info]   /etc/mha/scripts/master_ip_failover --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --orig_master_host=192.168.206.140 --orig_master_ip=192.168.206.140 --orig_master_port=3306 --command=stopssh --ssh_user=root  
Thu Mar 16 08:09:46 2017 - [info]  done.
Thu Mar 16 08:09:46 2017 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Thu Mar 16 08:09:46 2017 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Thu Mar 16 08:09:46 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] * Phase 3: Master Recovery Phase..
Thu Mar 16 08:09:46 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Thu Mar 16 08:09:46 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] The latest binary log file/position on all slaves is mysql-bin.000002:1033
Thu Mar 16 08:09:46 2017 - [info] Latest slaves (Slaves that received relay log files to the latest):
Thu Mar 16 08:09:46 2017 - [info]   192.168.206.139(192.168.206.139:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:46 2017 - [info]     GTID ON
Thu Mar 16 08:09:46 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:46 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 08:09:46 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:46 2017 - [info]     GTID ON
Thu Mar 16 08:09:46 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:46 2017 - [info]     Not candidate for the new Master (no_master is set)
Thu Mar 16 08:09:46 2017 - [info] The oldest binary log file/position on all slaves is mysql-bin.000002:1033
Thu Mar 16 08:09:46 2017 - [info] Oldest slaves:
Thu Mar 16 08:09:46 2017 - [info]   192.168.206.139(192.168.206.139:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:46 2017 - [info]     GTID ON
Thu Mar 16 08:09:46 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:46 2017 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Mar 16 08:09:46 2017 - [info]   192.168.206.141(192.168.206.141:3306)  Version=5.7.17-log (oldest major version between slaves) log-bin:enabled
Thu Mar 16 08:09:46 2017 - [info]     GTID ON
Thu Mar 16 08:09:46 2017 - [info]     Replicating from 192.168.206.140(192.168.206.140:3306)
Thu Mar 16 08:09:46 2017 - [info]     Not candidate for the new Master (no_master is set)
Thu Mar 16 08:09:46 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] * Phase 3.3: Determining New Master Phase..
Thu Mar 16 08:09:46 2017 - [info] 
Thu Mar 16 08:09:46 2017 - [info] 192.168.206.139 can be new master.
Thu Mar 16 08:09:46 2017 - [info] New master is 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 08:09:46 2017 - [info] Starting master failover..
Thu Mar 16 08:09:46 2017 - [info] 
From:
192.168.206.140(192.168.206.140:3306) (current master)
 +--192.168.206.139(192.168.206.139:3306)
 +--192.168.206.141(192.168.206.141:3306)

To:
192.168.206.139(192.168.206.139:3306) (new master)
 +--192.168.206.141(192.168.206.141:3306)

Starting master switch from 192.168.206.140(192.168.206.140:3306) to 192.168.206.139(192.168.206.139:3306)? (yes/NO): yes
Thu Mar 16 08:09:52 2017 - [info] New master decided manually is 192.168.206.139(192.168.206.139:3306)
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info] * Phase 3.3: New Master Recovery Phase..
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info]  Waiting all logs to be applied.. 
Thu Mar 16 08:09:52 2017 - [info]   done.
Thu Mar 16 08:09:52 2017 - [info] Getting new master's binlog name and position..
Thu Mar 16 08:09:52 2017 - [info]  mysql-bin.000003:984
Thu Mar 16 08:09:52 2017 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.206.139', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='u_repl', MASTER_PASSWORD='xxx';
Thu Mar 16 08:09:52 2017 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: mysql-bin.000003, 984, 347cbac6-0906-11e7-b957-000c2981a46e:1-2,
9e2c7c0f-0908-11e7-8230-000c29ab7544:2-3
Thu Mar 16 08:09:52 2017 - [info] Executing master IP activate script:
Thu Mar 16 08:09:52 2017 - [info]   /etc/mha/scripts/master_ip_failover --virtual_ip=192.168.206.145 --orig_master_vip_eth=eth0:234 --new_master_vip_eth=eth0:234 --command=start --ssh_user=root --orig_master_host=192.168.206.140 --orig_master_ip=192.168.206.140 --orig_master_port=3306 --new_master_host=192.168.206.139 --new_master_ip=192.168.206.139 --new_master_port=3306 --new_master_user='root' --new_master_password='replpass'  
Set read_only=0 on the new master.
Creating app user on the new master..
Undefined subroutine &main::FIXME_xxx_create_user called at /etc/mha/scripts/master_ip_failover line 93.
Thu Mar 16 08:09:52 2017 - [error][/usr/share/perl5/vendor_perl/MHA/MasterFailover.pm, ln1588]  Failed to activate master IP address for 192.168.206.139(192.168.206.139:3306) with return code 10:0
Thu Mar 16 08:09:52 2017 - [warning] Proceeding.
Thu Mar 16 08:09:52 2017 - [info] ** Finished master recovery successfully.
Thu Mar 16 08:09:52 2017 - [info] * Phase 3: Master Recovery Phase completed.
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info] * Phase 4: Slaves Recovery Phase..
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info] * Phase 4.1: Starting Slaves in parallel..
Thu Mar 16 08:09:52 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info] -- Slave recovery on host 192.168.206.141(192.168.206.141:3306) started, pid: 6478. Check tmp log /var/log/mha/app1/192.168.206.141_3306_20170316080936.log if it takes time..
Thu Mar 16 08:09:53 2017 - [info] 
Thu Mar 16 08:09:53 2017 - [info] Log messages from 192.168.206.141 ...
Thu Mar 16 08:09:53 2017 - [info] 
Thu Mar 16 08:09:52 2017 - [info]  Resetting slave 192.168.206.141(192.168.206.141:3306) and starting replication from the new master 192.168.206.139(192.168.206.139:3306)..
Thu Mar 16 08:09:52 2017 - [info]  Executed CHANGE MASTER.
Thu Mar 16 08:09:52 2017 - [info]  Slave started.
Thu Mar 16 08:09:52 2017 - [info]  gtid_wait(347cbac6-0906-11e7-b957-000c2981a46e:1-2,
9e2c7c0f-0908-11e7-8230-000c29ab7544:2-3) completed on 192.168.206.141(192.168.206.141:3306). Executed 0 events.
Thu Mar 16 08:09:53 2017 - [info] End of log messages from 192.168.206.141.
Thu Mar 16 08:09:53 2017 - [info] -- Slave on host 192.168.206.141(192.168.206.141:3306) started.
Thu Mar 16 08:09:53 2017 - [info] All new slave servers recovered successfully.
Thu Mar 16 08:09:53 2017 - [info] 
Thu Mar 16 08:09:53 2017 - [info] * Phase 5: New master cleanup phase..
Thu Mar 16 08:09:53 2017 - [info] 
Thu Mar 16 08:09:53 2017 - [info] Resetting slave info on the new master..
Thu Mar 16 08:09:53 2017 - [info]  192.168.206.139: Resetting slave info succeeded.
Thu Mar 16 08:09:53 2017 - [info] Master failover to 192.168.206.139(192.168.206.139:3306) completed successfully.
Thu Mar 16 08:09:53 2017 - [info] 

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

app1: MySQL Master failover 192.168.206.140(192.168.206.140:3306) to 192.168.206.139(192.168.206.139:3306) succeeded

Master 192.168.206.140(192.168.206.140:3306) is down!

Check MHA Manager logs at localhost.localdomain for details.

Started manual(interactive) failover.
Invalidated master IP address on 192.168.206.140(192.168.206.140:3306)
Selected 192.168.206.139(192.168.206.139:3306) as a new master.
192.168.206.139(192.168.206.139:3306): OK: Applying all logs succeeded.
Failed to activate master IP address for 192.168.206.139(192.168.206.139:3306) with return code 10:0
192.168.206.141(192.168.206.141:3306): OK: Slave started, replicating from 192.168.206.139(192.168.206.139:3306)
192.168.206.139(192.168.206.139:3306): Resetting slave info succeeded.
Master failover to 192.168.206.139(192.168.206.139:3306) completed successfully.
View Code

本文地址：http://www.cnblogs.com/ajiangg/p/6552855.html 

参考资源：https://code.google.com/p/mysql-master-ha/wiki/TableOfContents?tm=6

http://k-1blog.com/development/program/post-7414/

http://www.cnblogs.com/galengao/p/5764163.html

转载于:https://www.cnblogs.com/ajiangg/p/6552855.html

a549010853
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
python无法运行debug_Qt Creator无法启动调试
weixin_39834084的博客
12-29 610
qtc++项目在Qt Creator 3.4.1下成功构建。但当我无法启动调试器时。应用程序输出中的输出：调试开始调试失败调试已完成调试器从未真正启动。在终端输出：QProcess: Destroyed while process ("/usr/local/bin/gdb") is still running.Unexpected GDB stderr: "Python Exception No...
centos6.8下安装mysql
12-11
在Linux系统中，CentOS 6.8是一个广泛使用的稳定版本，而MySQL是一...如果你遇到了任何问题，可以参考提供的文档“尚硅谷centos6.8下安装mysql.docx”进行查阅，这份文档应该包含了更详细的步骤和解决常见问题的方法。
nginx设置反向代理怎么获取客户端的真实IP和域名以供日志分析
Enweitech Software Works
04-23 7490
nginx反向代理后，在应用中取得的ip都是反向代理服务器的ip，取得的域名也是反向代理配置的url的域名，解决该问题，需要在nginx反向代理配置中添加一些配置信息，目的将客户端的真实ip和域名传递到应用程序中。 nginx反向代理配置时，一般会添加下面的配置：      proxy_set_header Host $host;      proxy_set_header X-Real-IP $...
nginx获取经过层层代理后的客户端真实IP（使用正则匹配）
weixin_30644369的博客
11-24 251
今天帮兄弟项目搞了一个获取客户端真实IP的问题，网上这种问题很多，但是对于我们的场景都不太合用，现把我的解决方案share给大家，如有问题，请及时指出。 场景： 在请求到达后端服务之前，会经过层层代理的转发。 一般的解决方案： proxy_set_header Host $host; proxy_set_...
浅析CentOS6.8安装MySQL8.0.18的教程(RPM方式)
01-21
今天，记录下在CentOS 6.8服务器上如何安装MySQL 8.0.18，废话不多说了，直接进入主题。 一、卸载CentOS 6.8自带的MySQL 首先，卸载CentOS 6.8服务器上自带的MySQL，在命令行中输入如下命令查看CentOS 6.8服务器自带...
centos6.8下安装mysql1
08-08
在CentOS 6.8操作系统上安装MySQL 5.6.14是一个涉及多个步骤的过程，主要分为卸载旧版本、安装依赖、编译安装、配置权限、初始化数据库以及设置启动服务等环节。以下是详细的步骤和相关知识点： 1. **卸载旧版本**...
centos 6.8 搭建LAMP
11-30
centos 6.8 搭建LAMP环境及配置，以及搭建phpmyadmin**************************
图数据库查询与操作指南-以Nebula图数据库为例
DZSpace，专注于计算机科学与技术领域的技术博主，致力于分享实用知识与技巧，帮助读者快速掌握技术要点，共同探索计算机世界的无限可能。欢迎访问DZSpace的博客，一起学习进步！
07-26 308
图数据库查询与操作指南-以Nebula图数据库为例
ODBC连接达梦数据库
qq_55187735的博客
07-24 292
用户执行，因为环境变量配置在。
已经10岁的K8S，在很多方面仍需努力
u012516914的专栏
07-28 242
/ K8S 已经 10 岁了，但仍然有许多方面要继续努力 /Kubernetes 于 2014 年 6 月推出，自那时起，它在推广云原生应用设计和支持更多微服务部署方面发挥了巨大作用。容器部署的增长非常迅速，而 Kubernetes 对于企业管理这些部署至关重要——根据 CNCF 上一份报告的调查结果，84% 的组织正在使用或评估 Kubernetes，而 66% 的潜在和实际消费者在生产中使用 ...
SQL基础入门：解锁数据库管理的钥匙
WayneYalejk的博客
07-26 455
在数字化时代，数据已成为企业最宝贵的资产之一。为了高效地存储、查询和管理这些数据，SQL（Structured Query Language，结构化查询语言）应运而生。SQL不仅是数据库管理员的必备技能，也是数据分析师、开发人员等多个领域从业者的重要工具。本文将带您踏入SQL的世界，从基础概念到实际应用，一步步解锁数据库管理的钥匙。强调SQL在数据处理和分析中的重要性，鼓励读者通过实践不断深化对SQL的理解和应用。
CTF-NSSCTF题单[GKCTF2020]
2302_78903258的博客
07-24 1261
在低于7.2.29的PHP版本7.2.x，低于7.3.16的7.3.x和低于7.4.4的7.4.x中，将get_headers（）与用户提供的URL一起使用时，如果URL包含零（\ 0）字符，则URL将被静默地截断。访问/eval的路由，会设置一个delay，和你传入的get参数的delay进行比较，取较大的那个，然后setTimeout是延时函数，delay秒后就会执行第一个参数，即next()，否则就会send出timeout。是假的，但是有线索，提示说真正的flag的在。
添加索引导致微服务异常
07-29 481
执行DDL时，最好使用ONLINE选项，随着oracle版本升级，online状态下可执行的DDL逐步增加，大部分普通DDL上，可以使用ONLINE选项，例如。而在新增索引的时候会有TM锁，而该表又有大量的insert、update等，因此会对这些dml语句造成阻塞。1、对大表新增索引尽量停业务，就算加上online不会造成阻塞，但对性能也有影响，特别是这种性能敏感的系统。2、在新增索引的时候加online参数，而online产生的TM锁时间比较短。加了online后，可以以非独占的方式创建和删除索引。
教务管理平台/高校教务管理系统的设计与实现/教务网站/学生成绩管理系统/学生课程管理系统
weixin_47958760的博客
07-27 783
本毕业设计的内容是设计并且实现一个基于JSP技术的教务管理平台。采用MYSQL为数据库开发平台，SSM框架，Tomcat网络信息服务作为应用服务器。教务管理平台的功能已基本实现，主要有学生、教师、课程信息、课程选择、教师课表、学生成绩、图书信息、考试等管理功能。 论文主要从系统的分析与设计 、数据库设计和系统的详细设计等几个方面来进行论述，系统分析与设计部分主要论述了系统的功能分析、系统的设计思路，数据库设计主要论述了数据库的设计，系统的详细设计部分主要论述了几个主要模块的详细设计过程。
Springboot使用Dynamic-Datasource配置多数据源
最新发布
shenxiaomo1688的博客
07-29 706
grace-destroy: false #是否优雅关闭数据源，默认为false，设置为true时，关闭数据源时如果数据源中还存在活跃连接，至多等待10s后强制关闭。driver-class-name: com.mysql.jdbc.Driver # 3.2.0开始支持SPI可省略此配置。strict: false #严格匹配数据源,默认false. true未匹配到指定数据源时抛异常,false使用默认数据源。primary: master #设置默认的数据源或者数据源组,默认值即为master。
【MySQL进阶之路 | 高级篇】简述Bin Log日志
2301_80912559的博客
07-27 868
binlog即binary log，二进制日志文件，也叫作变更日志(update log)。二进制日志可以通过数据库的全量备份和二进制日志中保存的增量信息，完成数据库的无损失恢复I但是，如果遇到数据量大、数据库和数据表很多(比如分库分表的应用)的场景，用二进制日志进行数据恢复，是很有挑战性的，因为起止位置不容易管理。在这种情况下，一个有效的解决办法是配置主从数据库服务器，甚至是一主多从的架构，把二进制日志文件的内容通过中继日志，同步到从数据库服务器中，这样就可以有效避免数据库故障导致的数据异常等问题。
使用abpcli创建项目时提示数据库迁移失败
qq_43893277的博客
07-28 165
使用abpcli创建项目时提示数据库迁移失败！
CentOS 6.8环境下Zookeeper集群搭建步骤
在CentOS 6.8 64位系统上搭建Zookeeper集群，首先需要下载对应版本的Zookeeper，这里使用的版本是3.4.11。可以从官方镜像站点下载，例如http://mirrors.hust.edu.cn/apache/zookeeper/zookeeper-3.4.11/。下载完成后...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值