简介：

MHA（Master High Availability）目前在MySQL高可用方面是一个相对成熟的解决方案，它由日本DeNA公司youshimaton（现就职于Facebook公司）开发，是一套优秀的作为MySQL高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数据的一致性，以达到真正意义上的高可用。

该软件由两部分组成：MHA Manager（管理节点）和MHA Node（数据节点）。MHA Manager可以单独部署在一台独立的机器上管理多个master-slave集群，也可以部署在一台slave节点上。MHA Node运行在每台MySQL服务器上，MHA Manager会定时探测集群中的master节点，当master出现故障时，它可以自动将最新数据的slave提升为新的master，然后将所有其他的slave重新指向新的master。整个故障转移过程对应用程序完全透明。

在MHA自动故障切换过程中，MHA试图从宕机的主服务器上保存二进制日志，最大程度的保证数据的不丢失，但这并不总是可行的。例如，如果主服务器硬件故障或无法通过ssh访问，MHA没法保存二进制日志，只进行故障转移而丢失了最新的数据。使用MySQL 5.5的半同步复制，可以大大降低数据丢失的风险。MHA可以与半同步复制结合起来。如果只有一个slave已经收到了最新的二进制日志，MHA可以将最新的二进制日志应用于其他所有的slave服务器上，因此可以保证所有节点的数据一致性。

目前MHA主要支持一主多从的架构，要搭建MHA,要求一个复制集群中必须最少有三台数据库服务器，一主二从，即一台充当master，一台充当备用master，另外一台充当从库，因为至少需要三台服务器，出于机器成本的考虑，淘宝也在该基础上进行了改造，目前淘宝TMHA已经支持一主一从。另外对于想快速搭建的可以参考：MHA快速搭建

我们自己使用其实也可以使用1主1从，但是master主机宕机后无法切换，以及无法补全binlog。master的mysqld进程crash后，还是可以切换成功，以及补全binlog的。

官方介绍：https://code.google.com/p/mysql-master-ha/

图01展示了如何通过MHA Manager管理多组主从复制。可以将MHA工作原理总结为如下：

（ 图01 ）

（1）从宕机崩溃的master保存二进制日志事件（binlog events）;

（2）识别含有最新更新的slave；

（3）应用差异的中继日志（relay log）到其他的slave；

（4）应用从master保存的二进制日志事件（binlog events）；

（5）提升一个slave为新的master；

（6）使其他的slave连接新的master进行复制；

MHA软件由两部分组成，Manager工具包和Node工具包，具体的说明如下。

Manager工具包主要包括以下几个工具：

  1. masterha_check_ssh              检查MHA的SSH配置状况
  2. masterha_check_repl             检查MySQL复制状况
  3. masterha_manger                 启动MHA
  4. masterha_check_status           检测当前MHA运行状态
  5. masterha_master_monitor         检测master是否宕机
  6. masterha_master_switch          控制故障转移（自动或者手动）
  7. masterha_conf_host              添加或删除配置的server信息

Node工具包（这些工具通常由MHA Manager的脚本触发，无需人为操作）主要包括以下几个工具：

  1. save_binary_logs                保存和复制master的二进制日志
  2. apply_diff_relay_logs           识别差异的中继日志事件并将其差异的事件应用于其他的slave
  3. filter_mysqlbinlog              去除不必要的ROLLBACK事件（MHA已不再使用这个工具）
  4. purge_relay_logs                清除中继日志（不会阻塞SQL线程）

注意：

为了尽可能的减少主库硬件损坏宕机造成的数据丢失，因此在配置MHA的同时建议配置成MySQL 5.5的半同步复制。关于半同步复制原理各位自己进行查阅。（不是必须）

1.部署MHA

接下来部署MHA，具体的搭建环境如下（所有操作系统均为centos 6.2 64bit，不是必须，server03和server04是server02的从，复制环境搭建后面会简单演示，但是相关的安全复制不会详细说明，需要的童鞋请参考前面的文章，MySQL Replication需要注意的问题）：

  1. 角色                    ip地址          主机名          server_id                  类型
  2. Monitor host            192.168.0.20    server01            -                      监控复制组
  3. Master                  192.168.0.50    server02                                  写入
  4. Candicate master        192.168.0.60    server03                                  读
  5. Slave                   192.168.0.70    server04                                  读

其中master对外提供写服务，备选master（实际的slave，主机名server03）提供读服务，slave也提供相关的读服务，一旦master宕机，将会把备选master提升为新的master，slave指向新的master

（1）在所有节点安装MHA node所需的perl模块（DBD:mysql），安装脚本如下：

  1. [root@192.168.0.50 ~]# cat install.sh
  2. #!/bin/bash
  3. wget http://xrl.us/cpanm --no-check-certificate
  4. mv cpanm /usr/bin
  5. chmod  /usr/bin/cpanm
  6. cat > /root/list << EOF
  7. install DBD::mysql
  8. EOF
  9. for package in `cat /root/list`
  10. do
  11.     cpanm $package
  12. done
  13. [root@192.168.0.50 ~]#

如果有安装epel源，也可以使用yum安装

  1. yum install perl-DBD-MySQL -y

（2）在所有的节点安装mha node：

  1. wget http://mysql-master-ha.googlecode.com/files/mha4mysql-node-0.53.tar.gz
  2. tar xf mha4mysql-node-0.53.tar.gz
  3. cd mha4mysql-node-0.53
  4. perl Makefile.PL
  5. make && make install

安装完成后会在/usr/local/bin目录下生成以下脚本文件：

  1. [root@192.168.0.50 bin]# pwd
  2. /usr/local/bin
  3. [root@192.168.0.50 bin]# ll
  4. total
  5. -r-xr-xr-x  root root  Apr  : apply_diff_relay_logs
  6. -r-xr-xr-x  root root   Apr  : filter_mysqlbinlog
  7. -r-xr-xr-x  root root   Apr  : purge_relay_logs
  8. -r-xr-xr-x  root root   Apr  : save_binary_logs
  9. [root@192.168.0.50 bin]#

关于上面脚本的功能，上面已经介绍过了，这里不再重复了。

2.安装MHA Manager

MHA Manager中主要包括了几个管理员的命令行工具，例如master_manger，master_master_switch等。MHA Manger也依赖于perl模块，具体如下：

（1）安装MHA Node软件包之前需要安装依赖。我这里使用yum完成，没有epel源的可以使用上面提到的脚本（epel源安装也简单）。注意：在MHA Manager的主机也是需要安装MHA Node。

  1. rpm -ivh http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
  1. yum install perl-DBD-MySQL -y

安装MHA Node软件包，和上面的方法一样，如下：

  1. wget http://mysql-master-ha.googlecode.com/files/mha4mysql-node-0.53.tar.gz
  2. tar xf mha4mysql-node-0.53.tar.gz
  3. cd mha4mysql-node-0.53
  4. perl Makefile.PL
  5. make && make install

（2）安装MHA Manager。首先安装MHA Manger依赖的perl模块（我这里使用yum安装）：

  1. yum install perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Time-HiRes -y

安装MHA Manager软件包：

  1. wget http://mysql-master-ha.googlecode.com/files/mha4mysql-manager-0.53.tar.gz
  2. tar xf mha4mysql-manager-0.53.tar.gz
  3. cd mha4mysql-manager-0.53
  4. perl Makefile.PL
  5. make && make install

安装完成后会在/usr/local/bin目录下面生成以下脚本文件，前面已经说过这些脚本的作用，这里不再重复

  1. [root@192.168.0.20 bin]# pwd
  2. /usr/local/bin
  3. [root@192.168.0.20 bin]# ll
  4. total
  5. -r-xr-xr-x  root root  Apr  : apply_diff_relay_logs
  6. -r-xr-xr-x  root root   Apr  : filter_mysqlbinlog
  7. -r-xr-xr-x  root root   Apr  : masterha_check_repl
  8. -r-xr-xr-x  root root   Apr  : masterha_check_ssh
  9. -r-xr-xr-x  root root   Apr  : masterha_check_status
  10. -r-xr-xr-x  root root   Apr  : masterha_conf_host
  11. -r-xr-xr-x  root root   Apr  : masterha_manager
  12. -r-xr-xr-x  root root   Apr  : masterha_master_monitor
  13. -r-xr-xr-x  root root   Apr  : masterha_master_switch
  14. -r-xr-xr-x  root root   Apr  : masterha_secondary_check
  15. -r-xr-xr-x  root root   Apr  : masterha_stop
  16. -r-xr-xr-x  root root   Apr  : purge_relay_logs
  17. -r-xr-xr-x  root root   Apr  : save_binary_logs
  18. [root@192.168.0.20 bin]#

复制相关脚本到/usr/local/bin目录(软件包解压缩后就有了，不是必须，因为这些脚本不完整，需要自己修改，这是软件开发着留给我们自己发挥的,如果开启下面的任何一个脚本对应的参数，而对应这里的脚本又没有修改，则会抛错，自己被坑的很惨)

  1. [root@192.168.0.20 scripts]# pwd
  2. /root/mha4mysql-manager-0.53/samples/scripts
  3. [root@192.168.0.20 scripts]# ll
  4. total
  5. -rwxr-xr-x  root root   Jan     master_ip_failover                #自动切换时vip管理的脚本，不是必须，如果我们使用keepalived的，我们可以自己编写脚本完成对vip的管理，比如监控mysql，如果mysql异常，我们停止keepalived就行，这样vip就会自动漂移
  6. -rwxr-xr-x  root root   Jan     master_ip_online_change           #在线切换时vip的管理，不是必须，同样可以可以自行编写简单的shell完成
  7. -rwxr-xr-x  root root  Jan     power_manager                     #故障发生后关闭主机的脚本，不是必须
  8. -rwxr-xr-x  root root   Jan     send_report                       #因故障切换后发送报警的脚本，不是必须，可自行编写简单的shell完成。
  9. [root@192.168.0.20 scripts]# cp * /usr/local/bin/
  10. [root@192.168.0.20 scripts]#

3.配置SSH登录无密码验证（使用key登录，工作中常用）我的测试环境已经是使用key登录，服务器之间无需密码验证的。关于配置使用key登录，我想我不再重复。但是有一点需要注意：不能禁止 password 登陆，否则会出现错误

4.搭建主从复制环境

注意：binlog-do-db 和 replicate-ignore-db 设置必须相同。 MHA 在启动时候会检测过滤规则，如果过滤规则不同，MHA 不启动监控和故障转移。

（1）在server02上执行备份（192.168.0.50）

  1. [root@192.168.0.50 ~]# mysqldump --master-data= --single-transaction -R --triggers -A > all.sql

其中--master-data=2代表备份时刻记录master的Binlog位置和Position，--single-transaction意思是获取一致性快照，-R意思是备份存储过程和函数，--triggres的意思是备份触发器，-A代表备份所有的库。更多信息请自行mysqldump --help查看。

（2）在server02上创建复制用户：

  1. mysql> grant replication slave on *.* to 'repl'@'192.168.0.%' identified by '';
  2. Query OK, 0 rows affected (0.00 sec)
  3.  
  4. mysql> flush privileges;
  5. Query OK, 0 rows affected (0.00 sec)
  6.  
  7. mysql>

（3）查看主库备份时的binlog名称和位置，MASTER_LOG_FILE和MASTER_LOG_POS：

  1. [root@192.168.0.50 ~]# head -n  all.sql | grep 'CHANGE MASTER TO'
  2. -- CHANGE MASTER TO MASTER_LOG_FILE='mysql-bin.000010', MASTER_LOG_POS=;
  3. [root@192.168.0.50 ~]#

（4）把备份复制到server03和server04，也就是192.168.0.60和192.168.0.70

  1. scp all.sql server03:/data/
  2. scp all.sql server04:/data/

（5）导入备份到server03，执行复制相关命令

  1. mysql < /data/all.sql
  1. mysql> CHANGE MASTER TO MASTER_HOST='192.168.0.50',MASTER_USER='repl', MASTER_PASSWORD='',MASTER_LOG_FILE='mysql-bin.000010',MASTER_LOG_POS=112;
  2. Query OK, 0 rows affected (0.02 sec)
  3.  
  4. mysql> start slave;
  5. Query OK, 0 rows affected (0.01 sec)
  6.  
  7. mysql>

查看复制状态（可以看见复制成功）：

  1. [root@192.168.0.60 ~]# mysql -e 'show slave status\G' | egrep 'Slave_IO|Slave_SQL'
  2.                Slave_IO_State: Waiting for master to send event
  3.              Slave_IO_Running: Yes
  4.             Slave_SQL_Running: Yes
  5. [root@192.168.0.60 ~]#

（6）在server04（192.168.0.70）上搭建复制环境，操作和上面一样。

  1. mysql < /data/all.sql
  1. mysql> CHANGE MASTER TO MASTER_HOST='192.168.0.50',MASTER_USER='repl', MASTER_PASSWORD='',MASTER_LOG_FILE='mysql-bin.000010',MASTER_LOG_POS=112;
  2. Query OK, 0 rows affected (0.07 sec)
  3.  
  4. mysql> start slave;
  5. Query OK, 0 rows affected (0.00 sec)
  6.  
  7. mysql>

查看复制状态：

  1. [root@192.168.0.70 ~]# mysql -e 'show slave status\G' | egrep 'Slave_IO|Slave_SQL'
  2.                Slave_IO_State: Waiting for master to send event
  3.              Slave_IO_Running: Yes
  4.             Slave_SQL_Running: Yes
  5. [root@192.168.0.70 ~]#

（7）两台slave服务器设置read_only（从库对外提供读服务，只所以没有写进配置文件，是因为随时slave会提升为master）

  1. [root@192.168.0.60 ~]# mysql -e 'set global read_only=1'
  2. [root@192.168.0.60 ~]# 
  1. [root@192.168.0.70 ~]# mysql -e 'set global read_only=1'
  2. [root@192.168.0.70 ~]#

（8）创建监控用户（在master上执行，也就是192.168.0.50）：

  1. mysql> grant all privileges on *.* to 'root'@'192.168.0.%' identified  by '';
  2. Query OK, 0 rows affected (0.00 sec)
  3.  
  4. mysql> flush  privileges;
  5. Query OK, 0 rows affected (0.01 sec)
  6.  
  7. mysql>

到这里整个集群环境已经搭建完毕，剩下的就是配置MHA软件了。

5.配置MHA

（1）创建MHA的工作目录，并且创建相关配置文件（在软件包解压后的目录里面有样例配置文件）。

  1. [root@192.168.0.20 ~]# mkdir -p /etc/masterha
  2. [root@192.168.0.20 ~]# cp mha4mysql-manager-0.53/samples/conf/app1.cnf /etc/masterha/
  3. [root@192.168.0.20 ~]#

修改app1.cnf配置文件，修改后的文件内容如下（注意，配置文件中的注释需要去掉，我这里是为了解释清楚）：

  1. [root@192.168.0.20 ~]# cat /etc/masterha/app1.cnf
  2. [server default]
  3. manager_workdir=/var/log/masterha/app1.log              //设置manager的工作目录
  4. manager_log=/var/log/masterha/app1/manager.log          //设置manager的日志
  5. master_binlog_dir=/data/mysql                         //设置master 保存binlog的位置，以便MHA可以找到master的日志，我这里的也就是mysql的数据目录
  6. master_ip_failover_script= /usr/local/bin/master_ip_failover    //设置自动failover时候的切换脚本
  7. master_ip_online_change_script= /usr/local/bin/master_ip_online_change  //设置手动切换时候的切换脚本
  8. password=         //设置mysql中root用户的密码，这个密码是前文中创建监控用户的那个密码
  9. user=root               设置监控用户root
  10. ping_interval=         //设置监控主库，发送ping包的时间间隔，默认是3秒，尝试三次没有回应的时候自动进行railover
  11. remote_workdir=/tmp     //设置远端mysql在发生切换时binlog的保存位置
  12. repl_password=    //设置复制用户的密码
  13. repl_user=repl          //设置复制环境中的复制用户名
  14. report_script=/usr/local/send_report    //设置发生切换后发送的报警的脚本
  15. secondary_check_script= /usr/local/bin/masterha_secondary_check -s server03 -s server02            
    shutdown_script=""      //设置故障发生后关闭故障主机脚本（该脚本的主要作用是关闭主机放在发生脑裂,这里没有使用）
  16. ssh_user=root           //设置ssh的登录用户名
  17.  
  18. [server1]
  19. hostname=192.168.0.50
  20. port=
  21.  
  22. [server2]
  23. hostname=192.168.0.60
  24. port=
  25. candidate_master=   //设置为候选master，如果设置该参数以后，发生主从切换以后将会将此从库提升为主库，即使这个主库不是集群中事件最新的slave
  26. check_repl_delay=   //默认情况下如果一个slave落后master 100M的relay logs的话，MHA将不会选择该slave作为一个新的master，因为对于这个slave的恢复需要花费很长时间，通过设置check_repl_delay=0,MHA触发切换在选择一个新的master的时候将会忽略复制延时，这个参数对于设置了candidate_master=1的主机非常有用，因为这个候选主在切换的过程中一定是新的master
  27.  
  28. [server3]
  29. hostname=192.168.0.70
  30. port=
  31. [root@192.168.0.20 ~]#

（2）设置relay log的清除方式（在每个slave节点上）：

  1. [root@192.168.0.60 ~]# mysql -e 'set global relay_log_purge=0'
  2. [root@192.168.0.70 ~]# mysql -e 'set global relay_log_purge=0'

注意：

MHA在发生切换的过程中，从库的恢复过程中依赖于relay log的相关信息，所以这里要将relay log的自动清除设置为OFF，采用手动清除relay log的方式。在默认情况下，从服务器上的中继日志会在SQL线程执行完毕后被自动删除。但是在MHA环境中，这些中继日志在恢复其他从服务器时可能会被用到，因此需要禁用中继日志的自动删除功能。定期清除中继日志需要考虑到复制延时的问题。在ext3的文件系统下，删除大的文件需要一定的时间，会导致严重的复制延时。为了避免复制延时，需要暂时为中继日志创建硬链接，因为在linux系统中通过硬链接删除大文件速度会很快。（在mysql数据库中，删除大表时，通常也采用建立硬链接的方式）

MHA节点中包含了pure_relay_logs命令工具，它可以为中继日志创建硬链接，执行SET GLOBAL relay_log_purge=1,等待几秒钟以便SQL线程切换到新的中继日志，再执行SET GLOBAL relay_log_purge=0。

pure_relay_logs脚本参数如下所示：

  1. --user mysql                      用户名
  2. --password mysql                  密码
  3. --port                            端口号
  4. --workdir                         指定创建relay log的硬链接的位置，默认是/var/tmp，由于系统不同分区创建硬链接文件会失败，故需要执行硬链接具体位置，成功执行脚本后，硬链接的中继日志文件被删除
  5. --disable_relay_log_purge         默认情况下，如果relay_log_purge=，脚本会什么都不清理，自动退出，通过设定这个参数，当relay_log_purge=1的情况下会将relay_log_purge设置为0。清理relay log之后，最后将参数设置为OFF。

（3）设置定期清理relay脚本（两台slave服务器）

  1. [root@192.168.0.60 ~]# cat purge_relay_log.sh
  2. #!/bin/bash
  3. user=root
  4. passwd=
  5. port=
  6. log_dir='/data/masterha/log'
  7. work_dir='/data'
  8. purge='/usr/local/bin/purge_relay_logs'
  9.  
  10. if [ ! -d $log_dir ]
  11. then
  12.    mkdir $log_dir -p
  13. fi
  14.  
  15. $purge --user=$user --password=$passwd --disable_relay_log_purge --port=$port --workdir=$work_dir >> $log_dir/purge_relay_logs.log >&
  16. [root@192.168.0.60 ~]#

添加到crontab定期执行

  1. [root@192.168.0.60 ~]# crontab -l
  2.   * * * /bin/bash /root/purge_relay_log.sh
  3. [root@192.168.0.60 ~]#

purge_relay_logs脚本删除中继日志不会阻塞SQL线程。下面我们手动执行看看什么情况。

  1. [root@192.168.0.60 ~]# purge_relay_logs --user=root --password= --port= -disable_relay_log_purge --workdir=/data/
  2. -- ::: purge_relay_logs script started.
  3.  Found relay_log.info: /data/mysql/relay-log.info
  4.  Removing hard linked relay log files server03-relay-bin* under /data/.. done.
  5.  Current relay log file: /data/mysql/server03-relay-bin.
  6.  Archiving unused relay log files (up to /data/mysql/server03-relay-bin.) ...
  7.  Creating hard link for /data/mysql/server03-relay-bin. under /data//server03-relay-bin.000001 .. ok.
  8.  Creating hard links for unused relay log files completed.
  9.  Executing SET GLOBAL relay_log_purge=; FLUSH LOGS; sleeping a few seconds so that SQL thread can delete older relay log files (if it keeps up); SET GLOBAL relay_log_purge=; .. ok.
  10.  Removing hard linked relay log files server03-relay-bin* under /data/.. done.
  11. -- ::: All relay log purging operations succeeded.
  12. [root@192.168.0.60 ~]#

6.检查SSH配置

检查MHA Manger到所有MHA Node的SSH连接状态：

  1. [root@192.168.0.20 ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf
  2. Sun Apr  ::  - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  3. Sun Apr  ::  - [info] Reading application default configurations from /etc/masterha/app1.cnf..
  4. Sun Apr  ::  - [info] Reading server configurations from /etc/masterha/app1.cnf..
  5. Sun Apr  ::  - [info] Starting SSH connection tests..
  6. Sun Apr  ::  - [debug]
  7. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.50(192.168.0.50:) to root@192.168.0.60(192.168.0.60:)..
  8. Sun Apr  ::  - [debug]   ok.
  9. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.50(192.168.0.50:) to root@192.168.0.70(192.168.0.70:)..
  10. Sun Apr  ::  - [debug]   ok.
  11. Sun Apr  ::  - [debug]
  12. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.60(192.168.0.60:) to root@192.168.0.50(192.168.0.50:)..
  13. Sun Apr  ::  - [debug]   ok.
  14. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.60(192.168.0.60:) to root@192.168.0.70(192.168.0.70:)..
  15. Sun Apr  ::  - [debug]   ok.
  16. Sun Apr  ::  - [debug]
  17. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.70(192.168.0.70:) to root@192.168.0.50(192.168.0.50:)..
  18. Sun Apr  ::  - [debug]   ok.
  19. Sun Apr  ::  - [debug]  Connecting via SSH from root@192.168.0.70(192.168.0.70:) to root@192.168.0.60(192.168.0.60:)..
  20. Sun Apr  ::  - [debug]   ok.
  21. Sun Apr  ::  - [info] All SSH connection tests passed successfully.

可以看见各个节点ssh验证都是ok的。

7.检查整个复制环境状况。

通过masterha_check_repl脚本查看整个集群的状态

  1. [root@192.168.0.20 ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf
  2. Sun Apr  ::  - [info] Checking replication health on 192.168.0.60..
  3. Sun Apr  ::  - [info]  ok.
  4. Sun Apr  ::  - [info] Checking replication health on 192.168.0.70..
  5. Sun Apr  ::  - [info]  ok.
  6. Sun Apr  ::  - [info] Checking master_ip_failover_script status:
  7. Sun Apr  ::  - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port=
  8. Bareword "FIXME_xxx" not allowed while "strict subs" in use at /usr/local/bin/master_ip_failover line .
  9. Execution of /usr/local/bin/master_ip_failover aborted due to compilation errors.
  10. Sun Apr  ::  - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln214]  Failed to get master_ip_failover_script status with return code :.
  11. Sun Apr  ::  - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln383] Error happend on checking configurations.  at /usr/local/bin/masterha_check_repl line
  12. Sun Apr  ::  - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln478] Error happened on monitoring servers.
  13. Sun Apr  ::  - [info] Got exit code  (Not master dead).
  14.  
  15. MySQL Replication Health is NOT OK!

发现最后的结论说我的复制不是ok的。但是上面的信息明明说是正常的，自己也进数据库查看了。这里一直踩坑。一直纠结，后来无意中发现火丁笔记的博客，这才知道了原因，原来Failover两种方式：一种是虚拟IP地址，一种是全局配置文件。MHA并没有限定使用哪一种方式，而是让用户自己选择，虚拟IP地址的方式会牵扯到其它的软件,比如keepalive软件，而且还要修改脚本master_ip_failover。(最后修改脚本后才没有这个报错，自己不懂perl也是折腾的半死，去年买了块表)

如果发现如下错误：

  1. Can't exec "mysqlbinlog": No such file or directory at /usr/local/share/perl5/MHA/BinlogManager.pm line 99.
  2. mysqlbinlog version not found!
  1. Testing mysql connection and privileges..sh: mysql: command not found

解决方法如下，添加软连接（所有节点）

  1. ln -s /usr/local/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog
  1. ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql

所以先暂时注释master_ip_failover_script= /usr/local/bin/master_ip_failover这个选项。后面引入keepalived后和修改该脚本以后再开启该选项。

  1. [root@192.168.0.20 ~]# grep master_ip_failover /etc/masterha/app1.cnf
  2. #master_ip_failover_script= /usr/local/bin/master_ip_failover
  3. [root@192.168.0.20 ~]#

再次进行状态查看：

  1. Sun Apr  ::  - [info] Checking replication health on 192.168.0.60..
  2. Sun Apr  ::  - [info]  ok.
  3. Sun Apr  ::  - [info] Checking replication health on 192.168.0.70..
  4. Sun Apr  ::  - [info]  ok.
  5. Sun Apr  ::  - [warning] master_ip_failover_script is not defined.
  6. Sun Apr  ::  - [warning] shutdown_script is not defined.
  7. Sun Apr  ::  - [info] Got exit code  (Not master dead).
  8.  
  9. MySQL Replication Health is OK.

已经没有明显报错，只有两个警告而已，复制也显示正常了。
8.检查MHA Manager的状态：

通过master_check_status脚本查看Manager的状态：

  1. [root@192.168.0.20 ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
  2. app1 is stopped(:NOT_RUNNING).
  3. [root@192.168.0.20 ~]#

注意：如果正常，会显示"PING_OK"，否则会显示"NOT_RUNNING"，这代表MHA监控没有开启。
9.开启MHA Manager监控

  1. [root@192.168.0.20 ~]# nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover < /dev/null > /var/log/masterha/app1/manager.log >& &
  2. []
  3. [root@192.168.0.20 ~]#

启动参数介绍：

--remove_dead_master_conf      该参数代表当发生主从切换后，老的主库的ip将会从配置文件中移除。

--manger_log                            日志存放位置

--ignore_last_failover                 在缺省情况下，如果MHA检测到连续发生宕机，且两次宕机间隔不足8小时的话，则不会进行Failover，之所以这样限制是为了避免ping-pong效应。该参数代表忽略上次MHA触发切换产生的文件，默认情况下，MHA发生切换后会在日志目录，也就是上面我设置的/data产生app1.failover.complete文件，下次再次切换的时候如果发现该目录下存在该文件将不允许触发切换，除非在第一次切换后收到删除该文件，为了方便，这里设置为--ignore_last_failover。

查看MHA Manager监控是否正常：

  1. [root@192.168.0.20 ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
  2. app1 (pid:) is running(:PING_OK), master:192.168.0.50
  3. [root@192.168.0.20 ~]#

可以看见已经在监控了，而且master的主机为192.168.0.50

10.查看启动日志

  1. [root@192.168.0.20 ~]# tail -n20 /var/log/masterha/app1/manager.log
  2. Sun Apr  ::  - [info]   Connecting to root@192.168.0.70(192.168.0.70:)..
  3.   Checking slave recovery environment settings..
  4.     Opening /data/mysql/relay-log.info ... ok.
  5.     Relay log found at /data/mysql, up to server04-relay-bin.
  6.     Temporary relay log file is /data/mysql/server04-relay-bin.
  7.     Testing mysql connection and privileges.. done.
  8.     Testing mysqlbinlog output.. done.
  9.     Cleaning up test file(s).. done.
  10. Sun Apr  ::  - [info] Slaves settings check done.
  11. Sun Apr  ::  - [info]
  12. 192.168.0.50 (current master)
  13.  +--192.168.0.60
  14.  +--192.168.0.70
  15.  
  16. Sun Apr  ::  - [warning] master_ip_failover_script is not defined.
  17. Sun Apr  ::  - [warning] shutdown_script is not defined.
  18. Sun Apr  ::  - [info] Set master ping interval  seconds.
  19. Sun Apr  ::  - [info] Set secondary check script: /usr/local/bin/masterha_secondary_check -s server03 -s server02 --user=root --master_host=server02 --master_ip=192.168.0.50 --master_port=
  20. Sun Apr  ::  - [info] Starting ping health check on 192.168.0.50(192.168.0.50:)..
  21. Sun Apr  ::  - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..
  22. [root@192.168.0.20 ~]#

其中"Ping(SELECT) succeeded, waiting until MySQL doesn't respond.."说明整个系统已经开始监控了。
11.关闭MHA Manage监控

关闭很简单，使用masterha_stop命令完成。

  1. [root@192.168.0.20 ~]# masterha_stop --conf=/etc/masterha/app1.cnf
  2. Stopped app1 successfully.
  3. []+  Exit                   nohup masterha_manager --conf=/etc/masterha/app1.cnf --remove_dead_master_conf --ignore_last_failover --manager_log=/data/mamanager.log
  4. [root@192.168.0.20 ~]#

12.配置VIP
vip配置可以采用两种方式，一种通过keepalived的方式管理虚拟ip的浮动；另外一种通过脚本方式启动虚拟ip的方式（即不需要keepalived或者heartbeat类似的软件）。

1.keepalived方式管理虚拟ip，keepalived配置方法如下：

（1）下载软件进行并进行安装（两台master，准确的说一台是master，另外一台是备选master，在没有切换以前是slave）：

  1. [root@192.168.0.50 ~]# wget http://www.keepalived.org/software/keepalived-1.2.12.tar.gz
  1. tar xf keepalived-1.2..tar.gz
  2. cd keepalived-1.2.
  3. ./configure --prefix=/usr/local/keepalived
  4. make &&  make install
  5. cp /usr/local/keepalived/etc/rc.d/init.d/keepalived /etc/init.d/
  6. cp /usr/local/keepalived/etc/sysconfig/keepalived /etc/sysconfig/
  7. mkdir /etc/keepalived
  8. cp /usr/local/keepalived/etc/keepalived/keepalived.conf /etc/keepalived/
  9. cp /usr/local/keepalived/sbin/keepalived /usr/sbin/

（2）配置keepalived的配置文件，在master上配置（192.168.0.50）

  1. [root@192.168.0.50 ~]# cat /etc/keepalived/keepalived.conf
  2. ! Configuration File for keepalived
  3.  
  4. global_defs {
  5.      notification_email {
  6.      saltstack@.com
  7.    }
  8.    notification_email_from dba@dbserver.com
  9.    smtp_server 127.0.0.1
  10.    smtp_connect_timeout
  11.    router_id MySQL-HA
  12. }
  13.  
  14. vrrp_instance VI_1 {
  15.     state BACKUP
  16.     interface eth1
  17.     virtual_router_id
  18.     priority
  19.     advert_int
  20.     nopreempt
  21.  
  22.     authentication {
  23.     auth_type PASS
  24.     auth_pass
  25.     }
  26.  
  27.     virtual_ipaddress {
  28.         192.168.0.88
  29.     }
  30. }
  31.  
  32. [root@192.168.0.50 ~]#

其中router_id MySQL HA表示设定keepalived组的名称，将192.168.0.88这个虚拟ip绑定到该主机的eth1网卡上，并且设置了状态为backup模式，将keepalived的模式设置为非抢占模式（nopreempt），priority 150表示设置的优先级为150。下面的配置略有不同，但是都是一个意思。
在候选master上配置（192.168.0.60）

  1. [root@192.168.0.60 ~]# cat /etc/keepalived/keepalived.conf
  2. ! Configuration File for keepalived
  3.  
  4. global_defs {
  5.      notification_email {
  6.      saltstack@.com
  7.    }
  8.    notification_email_from dba@dbserver.com
  9.    smtp_server 127.0.0.1
  10.    smtp_connect_timeout
  11.    router_id MySQL-HA
  12. }
  13.  
  14. vrrp_instance VI_1 {
  15.     state BACKUP
  16.     interface eth1
  17.     virtual_router_id
  18.     priority
  19.     advert_int
  20.     nopreempt
  21.  
  22.     authentication {
  23.     auth_type PASS
  24.     auth_pass
  25.     }
  26.  
  27.     virtual_ipaddress {
  28.         192.168.0.88
  29.     }
  30. }
  31.  
  32. [root@192.168.0.60 ~]#

（3）启动keepalived服务，在master上启动并查看日志

  1. [root@192.168.0.50 ~]# /etc/init.d/keepalived start
  2. Starting keepalived:                                       [  OK  ]
  3. [root@192.168.0.50 ~]# tail -f /var/log/messages
  4. Apr  ::  Keepalived_healthcheckers[]: Opening file '/etc/keepalived/keepalived.conf'.
  5. Apr  ::  Keepalived_healthcheckers[]: Configuration is using :  Bytes
  6. Apr  ::  kernel: IPVS: Connection hash table configured (size=, memory=64Kbytes)
  7. Apr  ::  kernel: IPVS: ipvs loaded.
  8. Apr  ::  Keepalived_healthcheckers[]: Using LinkWatch kernel netlink reflector...
  9. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) Transition to MASTER STATE
  10. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering MASTER STATE
  11. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) setting protocol VIPs.
  12. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88
  13. Apr  ::  Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.88 added
  14. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth1 for 192.168.0.88

发现已经将虚拟ip 192.168.0.88绑定了网卡eth1上。
（4）查看绑定情况

  1. [root@192.168.0.50 ~]# ip addr | grep eth1
  2. : eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu  qdisc pfifo_fast state UP qlen
  3.     inet 192.168.0.50/ brd 192.168.0.255 scope global eth1
  4.     inet 192.168.0.88/ scope global eth1
  5. [root@192.168.0.50 ~]#

在另外一台服务器，候选master上启动keepalived服务，并观察

  1. [root@192.168.0.60 ~]# /etc/init.d/keepalived start ; tail -f /var/log/messages
  2. Starting keepalived:                                       [  OK  ]
  3. Apr  ::  Keepalived_vrrp[]: Registering gratuitous ARP shared channel
  4. Apr  ::  Keepalived_vrrp[]: Opening file '/etc/keepalived/keepalived.conf'.
  5. Apr  ::  Keepalived_vrrp[]: Configuration is using :  Bytes
  6. Apr  ::  Keepalived_vrrp[]: Using LinkWatch kernel netlink reflector...
  7. Apr  ::  Keepalived_vrrp[]: VRRP_Instance(VI_1) Entering BACKUP STATE
  8. Apr  ::  Keepalived_vrrp[]: VRRP sockpool: [ifindex(), proto(), unicast(), fd(,)]
  9. Apr  ::  Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.80.138 added
  10. Apr  ::  Keepalived_healthcheckers[]: Netlink reflector reports IP 192.168.0.60 added
  11. Apr  ::  Keepalived_healthcheckers[]: Netlink reflector reports IP fe80::20c:29ff:fe9d:6a9e added
  12. Apr  ::  Keepalived_healthcheckers[]: Netlink reflector reports IP fe80::20c:29ff:fe9d:6aa8 added
  13. Apr  ::  Keepalived_healthcheckers[]: Registering Kernel netlink reflector
  14. Apr  ::  Keepalived_healthcheckers[]: Registering Kernel netlink command channel
  15. Apr  ::  Keepalived_healthcheckers[]: Opening file '/etc/keepalived/keepalived.conf'.
  16. Apr  ::  Keepalived_healthcheckers[]: Configuration is using :  Bytes
  17. Apr  ::  kernel: IPVS: Registered protocols (TCP, UDP, AH, ESP)
  18. Apr  ::  kernel: IPVS: Connection hash table configured (size=, memory=64Kbytes)
  19. Apr  ::  kernel: IPVS: ipvs loaded.
  20. Apr  ::  Keepalived_healthcheckers[]: Using LinkWatch kernel netlink reflector...

从上面的信息可以看到keepalived已经配置成功。
注意：

上面两台服务器的keepalived都设置为了BACKUP模式，在keepalived中2种模式，分别是master->backup模式和backup->backup模式。这两种模式有很大区别。在master->backup模式下，一旦主库宕机，虚拟ip会自动漂移到从库，当主库修复后，keepalived启动后，还会把虚拟ip抢占过来，即使设置了非抢占模式（nopreempt）抢占ip的动作也会发生。在backup->backup模式下，当主库宕机后虚拟ip会自动漂移到从库上，当原主库恢复和keepalived服务启动后，并不会抢占新主的虚拟ip，即使是优先级高于从库的优先级别，也不会发生抢占。为了减少ip漂移次数，通常是把修复好的主库当做新的备库。

（5）MHA引入keepalived（MySQL服务进程挂掉时通过MHA 停止keepalived）:

要想把keepalived服务引入MHA，我们只需要修改切换是触发的脚本文件master_ip_failover即可，在该脚本中添加在master发生宕机时对keepalived的处理。

编辑脚本/usr/local/bin/master_ip_failover，修改后如下，我对perl不熟悉，所以我这里完整贴出该脚本（主库上操作，192.168.0.50）。

在MHA Manager修改脚本修改后的内容如下（参考资料比较少）：

  1. #!/usr/bin/env perl
  2.  
  3. use strict;
  4. use warnings FATAL => 'all';
  5.  
  6. use Getopt::Long;
  7.  
  8. my (
  9.     $command,          $ssh_user,        $orig_master_host, $orig_master_ip,
  10.     $orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
  11. );
  12.  
  13. my $vip = '192.168.0.88';
  14. my $ssh_start_vip = "/etc/init.d/keepalived start";
  15. my $ssh_stop_vip = "/etc/init.d/keepalived stop";
  16.  
  17. GetOptions(
  18.     'command=s'          => \$command,
  19.     'ssh_user=s'         => \$ssh_user,
  20.     'orig_master_host=s' => \$orig_master_host,
  21.     'orig_master_ip=s'   => \$orig_master_ip,
  22.     'orig_master_port=i' => \$orig_master_port,
  23.     'new_master_host=s'  => \$new_master_host,
  24.     'new_master_ip=s'    => \$new_master_ip,
  25.     'new_master_port=i'  => \$new_master_port,
  26. );
  27.  
  28. exit &main();
  29.  
  30. sub main {
  31.  
  32.     print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";
  33.  
  34.     if ( $command eq "stop" || $command eq "stopssh" ) {
  35.  
  36.         my $exit_code = ;
  37.         eval {
  38.             print "Disabling the VIP on old master: $orig_master_host \n";
  39.             &stop_vip();
  40.             $exit_code = ;
  41.         };
  42.         if ($@) {
  43.             warn "Got Error: $@\n";
  44.             exit $exit_code;
  45.         }
  46.         exit $exit_code;
  47.     }
  48.     elsif ( $command eq "start" ) {
  49.  
  50.         my $exit_code = ;
  51.         eval {
  52.             print "Enabling the VIP - $vip on the new master - $new_master_host \n";
  53.             &start_vip();
  54.             $exit_code = ;
  55.         };
  56.         if ($@) {
  57.             warn $@;
  58.             exit $exit_code;
  59.         }
  60.         exit $exit_code;
  61.     }
  62.     elsif ( $command eq "status" ) {
  63.         print "Checking the Status of the script.. OK \n";
  64.         #`ssh $ssh_user\@cluster1 \" $ssh_start_vip \"`;
  65.         exit ;
  66.     }
  67.     else {
  68.         &usage();
  69.         exit ;
  70.     }
  71. }
  72.  
  73. # A simple system call that enable the VIP on the new master
  74. sub start_vip() {
  75.     `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
  76. }
  77. # A simple system call that disable the VIP on the old_master
  78. sub stop_vip() {
         return 0  unless  ($ssh_user);
  79.     `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
  80. }
  81.  
  82. sub usage {
  83.     print
  84.     "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";
  85. }

现在已经修改这个脚本了，我们现在打开在上面提到过的参数，再检查集群状态，看是否会报错。

  1. [root@192.168.0.20 ~]# grep 'master_ip_failover_script' /etc/masterha/app1.cnf
  2. master_ip_failover_script= /usr/local/bin/master_ip_failover
  3. [root@192.168.0.20 ~]# 
  1. [root@192.168.0.20 ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf
  2. Sun Apr  ::  - [info] Slaves settings check done.
  3. Sun Apr  ::  - [info]
  4. 192.168.0.50 (current master)
  5.  +--192.168.0.60
  6.  +--192.168.0.70
  7.  
  8. Sun Apr  ::  - [info] Checking replication health on 192.168.0.60..
  9. Sun Apr  ::  - [info]  ok.
  10. Sun Apr  ::  - [info] Checking replication health on 192.168.0.70..
  11. Sun Apr  ::  - [info]  ok.
  12. Sun Apr  ::  - [info] Checking master_ip_failover_script status:
  13. Sun Apr  ::  - [info]   /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port=
  14. Sun Apr  ::  - [info]  OK.
  15. Sun Apr  ::  - [warning] shutdown_script is not defined.
  16. Sun Apr  ::  - [info] Got exit code  (Not master dead).
  17.  
  18. MySQL Replication Health is OK.

可以看见已经没有报错了。哈哈
 /usr/local/bin/master_ip_failover添加或者修改的内容意思是当主库数据库发生故障时，会触发MHA切换，MHA Manager会停掉主库上的keepalived服务，触发虚拟ip漂移到备选从库，从而完成切换。当然可以在keepalived里面引入脚本，这个脚本监控mysql是否正常运行，如果不正常，则调用该脚本杀掉keepalived进程。

2.通过脚本的方式管理VIP。这里是修改/usr/local/bin/master_ip_failover，也可以使用其他的语言完成，比如php语言。使用php脚本编写的failover这里就不介绍了。修改完成后内容如下，而且如果使用脚本管理vip的话，需要手动在master服务器上绑定一个vip（发现修改修改对perl竟然有感觉了。难道我适合学Perl？^_^）

  1. [root@192.168.0.50 ~]# /sbin/ifconfig eth1: 192.168.0.88/

通过脚本来维护vip的测试我这里就不说明了，童鞋们自行测试，脚本如下（测试通过）

  1. #!/usr/bin/env perl
  2.  
  3. use strict;
  4. use warnings FATAL => 'all';
  5.  
  6. use Getopt::Long;
  7.  
  8. my (
  9.     $command,          $ssh_user,        $orig_master_host, $orig_master_ip,
  10.     $orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
  11. );
  12.  
  13. my $vip = '192.168.0.88/24';
  14. my $key = '1';
  15. my $ssh_start_vip = "/sbin/ifconfig eth1:$key $vip";
  16. my $ssh_stop_vip = "/sbin/ifconfig eth1:$key down";
  17.  
  18. GetOptions(
  19.     'command=s'          => \$command,
  20.     'ssh_user=s'         => \$ssh_user,
  21.     'orig_master_host=s' => \$orig_master_host,
  22.     'orig_master_ip=s'   => \$orig_master_ip,
  23.     'orig_master_port=i' => \$orig_master_port,
  24.     'new_master_host=s'  => \$new_master_host,
  25.     'new_master_ip=s'    => \$new_master_ip,
  26.     'new_master_port=i'  => \$new_master_port,
  27. );
  28.  
  29. exit &main();
  30.  
  31. sub main {
  32.  
  33.     print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";
  34.  
  35.     if ( $command eq "stop" || $command eq "stopssh" ) {
  36.  
  37.         my $exit_code = ;
  38.         eval {
  39.             print "Disabling the VIP on old master: $orig_master_host \n";
  40.             &stop_vip();
  41.             $exit_code = ;
  42.         };
  43.         if ($@) {
  44.             warn "Got Error: $@\n";
  45.             exit $exit_code;
  46.         }
  47.         exit $exit_code;
  48.     }
  49.     elsif ( $command eq "start" ) {
  50.  
  51.         my $exit_code = ;
  52.         eval {
  53.             print "Enabling the VIP - $vip on the new master - $new_master_host \n";
  54.             &start_vip();
  55.             $exit_code = ;
  56.         };
  57.         if ($@) {
  58.             warn $@;
  59.             exit $exit_code;
  60.         }
  61.         exit $exit_code;
  62.     }
  63.     elsif ( $command eq "status" ) {
  64.         print "Checking the Status of the script.. OK \n";
  65.         exit ;
  66.     }
  67.     else {
  68.         &usage();
  69.         exit ;
  70.     }
  71. }
  72.  
  73. sub start_vip() {
  74.     `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
  75. }
  76. sub stop_vip() {
         return 0  unless  ($ssh_user);
  77.     `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
  78. }
  79.  
  80. sub usage {
  81.     print
  82.     "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";
  83. }

为了防止脑裂发生，推荐生产环境采用脚本的方式来管理虚拟ip，而不是使用keepalived来完成。到此为止，基本MHA集群已经配置完毕。接下来就是实际的测试环节了。通过一些测试来看一下MHA到底是如何进行工作的。下面将从MHA自动failover，我们手动failover，在线切换三种方式来介绍MHA的工作情况。

一.自动Failover（必须先启动MHA Manager，否则无法自动切换，当然手动切换不需要开启MHA Manager监控。各位童鞋请参考前面启动MHA Manager）

测试环境再次贴一下，文章太长，自己都搞晕了。

  1. 角色                    ip地址          主机名          server_id               类型
  2. Monitor host            192.168.0.20    server01            -                   监控复制组
  3. Master                  192.168.0.50    server02                               写入
  4. Candicate master        192.168.0.60    server03                               读
  5. Slave                   192.168.0.70    server04                               读

自动failover模拟测试的操作步骤如下。
（1）使用sysbench生成测试数据（使用yum快速安装）

  1.  yum install sysbench -y

在主库（192.168.0.50）上进行sysbench数据生成，在sbtest库下生成sbtest表，共100W记录。

  1. [root@192.168.0.50 ~]# sysbench --test=oltp --oltp-table-size= --oltp-read-only=off --init-rng=on --num-threads= --max-requests= --oltp-dist-type=uniform --max-time= --mysql-user=root --mysql-socket=/tmp/mysql.sock --mysql-password= --db-driver=mysql --mysql-table-engine=innodb --oltp-test-mode=complex prepare

（2）停掉slave sql线程，模拟主从延时。（192.168.0.60）

  1. mysql> stop slave io_thread;
  2. Query OK, 0 rows affected (0.08 sec)
  3.  
  4. mysql>

另外一台slave我们没有停止io线程，所以还在继续接收日志。

（3）模拟sysbench压力测试。

在主库上（192.168.0.50）进行压力测试，持续时间为3分钟，产生大量的binlog。

  1. [root@192.168.0.50 ~]# sysbench --test=oltp --oltp-table-size= --oltp-read-only=off --init-rng=on --num-threads= --max-requests= --oltp-dist-type=uniform --max-time= --mysql-user=root --mysql-socket=/tmp/mysql.sock --mysql-password= --db-driver=mysql --mysql-table-engine=innodb --oltp-test-mode=complex run
  2. sysbench 0.4.:  multi-threaded system evaluation benchmark
  3.  
  4. Running the test with following options:
  5. Number of threads:
  6. Initializing random number generator from timer.
  7.  
  8. Doing OLTP test.
  9. Running mixed OLTP test
  10. Using Uniform distribution
  11. Using "BEGIN" for starting transactions
  12. Using auto_inc on the id column
  13. Threads started!
  14. Time limit exceeded, exiting...
  15. (last message repeated  times)
  16. Done.
  17.  
  18. OLTP test statistics:
  19.     queries performed:
  20.         read:
  21.         write:
  22.         other:
  23.         total:
  24.     transactions:                           (5.92 per sec.)
  25.     deadlocks:                                 (0.00 per sec.)
  26.     read/write requests:                   (112.56 per sec.)
  27.     other operations:                       (11.85 per sec.)
  28.  
  29. Test execution summary:
  30.     total time:                          .9728s
  31.     total number of events:
  32.     total time taken by event execution: 2910.4518
  33.     per-request statistics:
  34.          min:                                .29ms
  35.          avg:                               .86ms
  36.          max:                               .95ms
  37.          approx.   percentile:            .47ms
  38.  
  39. Threads fairness:
  40.     events (avg/stddev):           67.3750/1.49
  41.     execution time (avg/stddev):   181.9032/0.11

（4）开启slave（192.168.0.60）上的IO线程，追赶落后于master的binlog。

  1. mysql> start slave io_thread;
  2. Query OK, 0 rows affected (0.00 sec)
  3.  
  4. mysql>

（5）杀掉主库mysql进程，模拟主库发生故障，进行自动failover操作。

  1. [root@192.168.0.50 ~]# pkill - mysqld

（6）查看MHA切换日志，了解整个切换过程，在192.168.0.20上查看日志：

  1. [root@192.168.0.20 ~]# cat /var/log/masterha/app1/manager.log
  2. Mon Apr  ::  - [warning] Got error on MySQL select ping:  (MySQL server has gone away)
  3. Mon Apr  ::  - [info] Executing seconary network check script: /usr/local/bin/masterha_secondary_check -s server03 -s server02 --user=root --master_host=server02 --master_ip=192.168.0.50 --master_  Creating /tmp if not exists..    ok.
  4.   Checking output directory is accessible or not..
  5.    ok.
  6.   Binlog found at /data/mysql, up to mysql-bin.
  7. Mon Apr  ::  - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  8. Mon Apr  ::  - [info] Reading application default configurations from /etc/masterha/app1.cnf..
  9. Mon Apr  ::  - [info] Reading server configurations from /etc/masterha/app1.cnf..
  10. ble from server03. OK.
  11. Monitoring server server02 is reachable, Master is not reachable from server02. OK.
  12. Mon Apr  ::  - [info] Master is not reachable from all other monitoring servers. Failover should start.
  13. Mon Apr  ::  - [warning] Got error on MySQL connect:  (Lost connection to MySQL server at 'reading initial communication packet', system error: )
  14. Mon Apr  ::  - [warning] Connection failed  time(s)..
  15. Mon Apr  ::  - [warning] Got error on MySQL connect:  (Lost connection to MySQL server at 'reading initial communication packet', system error: )
  16. Mon Apr  ::  - [warning] Connection failed  time(s)..
  17. Mon Apr  ::  - [warning] Got error on MySQL connect:  (Lost connection to MySQL server at 'reading initial communication packet', system error: )
  18. Mon Apr  ::  - [warning] Connection failed  time(s)..
  19. Mon Apr  ::  - [warning] Master is not reachable from health checker!
  20. Mon Apr  ::  - [warning] Master 192.168.0.50(192.168.0.50:) is not reachable!
  21. Mon Apr  ::  - [warning] SSH is reachable.
  22. Mon Apr  ::  - [info] Connecting to a master server failed. Reading configuration file /etc/masterha_default.cnf and /etc/masterha/app1.cnf again, and trying to connect to all servers to check server status..
  23. Mon Apr  ::  - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  24. Mon Apr  ::  - [info] Reading application default configurations from /etc/masterha/app1.cnf..
  25. Mon Apr  ::  - [info] Reading server configurations from /etc/masterha/app1.cnf..
  26. Mon Apr  ::  - [info] Dead Servers:
  27. Mon Apr  ::  - [info]   192.168.0.50(192.168.0.50:)
  28. Mon Apr  ::  - [info] Alive Servers:
  29. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)
  30. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)
  31. Mon Apr  ::  - [info] Alive Slaves:
  32. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  33. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  34. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  35. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  36. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  37. Mon Apr  ::  - [info] Checking slave configurations..
  38. Mon Apr  ::  - [info] Checking replication filtering settings..
  39. Mon Apr  ::  - [info]  Replication filtering check ok.
  40. Mon Apr  ::  - [info] Master is down!
  41. Mon Apr  ::  - [info] Terminating monitoring script.
  42. Mon Apr  ::  - [info] Got exit code  (Master dead).
  43. Mon Apr  ::  - [info] MHA::MasterFailover version 0.53.
  44. Mon Apr  ::  - [info] Starting master failover.
  45. Mon Apr  ::  - [info]
  46. Mon Apr  ::  - [info] * Phase : Configuration Check Phase..
  47. Mon Apr  ::  - [info]
  48. Mon Apr  ::  - [info] Dead Servers:
  49. Mon Apr  ::  - [info]   192.168.0.50(192.168.0.50:)
  50. Mon Apr  ::  - [info] Checking master reachability via mysql(double check)..
  51. Mon Apr  ::  - [info]  ok.
  52. Mon Apr  ::  - [info] Alive Servers:
  53. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)
  54. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)
  55. Mon Apr  ::  - [info] Alive Slaves:
  56. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  57. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  58. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  59. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  60. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  61. Mon Apr  ::  - [info] ** Phase : Configuration Check Phase completed.
  62. Mon Apr  ::  - [info]
  63. Mon Apr  ::  - [info] * Phase : Dead Master Shutdown Phase..
  64. Mon Apr  ::  - [info]
  65. Mon Apr  ::  - [info] Forcing shutdown so that applications never connect to the current master..
  66. Mon Apr  ::  - [info] Executing master IP deactivatation script:
  67. Mon Apr  ::  - [info]   /usr/local/bin/master_ip_failover --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --command=stopssh --ssh_user=root  
  68.  
  69. IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===
  70.  
  71. Disabling the VIP on old master: 192.168.0.50
  72. Mon Apr  ::  - [info]  done.
  73. Mon Apr  ::  - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
  74. Mon Apr  ::  - [info] * Phase : Dead Master Shutdown Phase completed.
  75. Mon Apr  ::  - [info]
  76. Mon Apr  ::  - [info] * Phase : Master Recovery Phase..
  77. Mon Apr  ::  - [info]
  78. Mon Apr  ::  - [info] * Phase 3.1: Getting Latest Slaves Phase..
  79. Mon Apr  ::  - [info]
  80. Mon Apr  ::  - [info] The latest binary log file/position on all slaves is mysql-bin.:
  81. Mon Apr  ::  - [info] Latest slaves (Slaves that received relay log files to the latest):
  82. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  83. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  84. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  85. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  86. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  87. Mon Apr  ::  - [info] The oldest binary log file/position on all slaves is mysql-bin.:
  88. Mon Apr  ::  - [info] Oldest slaves:
  89. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  90. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  91. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  92. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  93. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  94. Mon Apr  ::  - [info]
  95. Mon Apr  ::  - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
  96. Mon Apr  ::  - [info]
  97. Mon Apr  ::  - [info] Fetching dead master's binary logs..
  98. Mon Apr  ::  - [info] Executing command on the dead master 192.168.0.50(192.168.0.50:): save_binary_logs --command=save --start_file=mysql-bin.  --start_pos= --binlog_dir=/data/mysql --output_file=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog --handle_raw_binlog= --disable_log_bin= --manager_version=0.53
  99.   Creating /tmp if not exists..    ok.
  100.  Concat binary/relay logs from mysql-bin. pos  to mysql-bin. EOF into /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog ..
  101.   Dumping binlog format description event, from position  to .. ok.
  102.   Dumping effective binlog data from /data/mysql/mysql-bin. position  to tail().. ok.
  103.  Concat succeeded.
  104. Mon Apr  ::  - [info] scp from root@192.168.0.50:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog to local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog succeeded.
  105. Mon Apr  ::  - [info] HealthCheck: SSH to 192.168.0.60 is reachable.
  106. Mon Apr  ::  - [info] HealthCheck: SSH to 192.168.0.70 is reachable.
  107. Mon Apr  ::  - [info]
  108. Mon Apr  ::  - [info] * Phase 3.3: Determining New Master Phase..
  109. Mon Apr  ::  - [info]
  110. Mon Apr  ::  - [info] Finding the latest slave that has all relay logs for recovering other slaves..
  111. Mon Apr  ::  - [info] All slaves received relay logs to the same position. No need to resync each other.
  112. Mon Apr  ::  - [info] Searching new master from slaves..
  113. Mon Apr  ::  - [info]  Candidate masters from the configuration file:
  114. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  115. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  116. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  117. Mon Apr  ::  - [info]  Non-candidate masters:
  118. Mon Apr  ::  - [info]  Searching from candidate_master slaves which have received the latest relay log events..
  119. Mon Apr  ::  - [info] New master is 192.168.0.60(192.168.0.60:)
  120. Mon Apr  ::  - [info] Starting master failover..
  121. Mon Apr  ::  - [info]
  122. From:
  123. 192.168.0.50 (current master)
  124.  +--192.168.0.60
  125.  +--192.168.0.70
  126.  
  127. To:
  128. 192.168.0.60 (new master)
  129.  +--192.168.0.70
  130. Mon Apr  ::  - [info]
  131. Mon Apr  ::  - [info] * Phase 3.3: New Master Diff Log Generation Phase..
  132. Mon Apr  ::  - [info]
  133. Mon Apr  ::  - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
  134. Mon Apr  ::  - [info] Sending binlog..
  135. Mon Apr  ::  - [info] scp from local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog to root@192.168.0.60:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog succeeded.
  136. Mon Apr  ::  - [info]
  137. Mon Apr  ::  - [info] * Phase 3.4: Master Log Apply Phase..
  138. Mon Apr  ::  - [info]
  139. Mon Apr  ::  - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
  140. Mon Apr  ::  - [info] Starting recovery on 192.168.0.60(192.168.0.60:)..
  141. Mon Apr  ::  - [info]  Generating diffs succeeded.
  142. Mon Apr  ::  - [info] Waiting until all relay logs are applied.
  143. Mon Apr  ::  - [info]  done.
  144. Mon Apr  ::  - [info] Getting slave status..
  145. Mon Apr  ::  - [info] This slave(192.168.0.60)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000018:112). No need to recover from Exec_Master_Log_Pos.
  146. Mon Apr  ::  - [info] Connecting to the target slave host 192.168.0.60, running recover script..
  147. Mon Apr  ::  - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user=root --slave_host=192.168.0.60 --slave_ip=192.168.0.60  --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog --workdir=/tmp --target_version=5.5.-ndb-7.2.-gpl-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.53 --slave_pass=xxx
  148. Mon Apr  ::  - [info]
  149. Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog on 192.168.0.60:. This may take long time...
  150. Applying log files succeeded.
  151. Mon Apr  ::  - [info]  All relay logs were successfully applied.
  152. Mon Apr  ::  - [info] Getting new master's binlog name and position..
  153. Mon Apr  ::  - [info]  mysql-bin.:
  154. Mon Apr  ::  - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.0.60', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000022', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
  155. Mon Apr  ::  - [info] Executing master IP activate script:
  156. Mon Apr  ::  - [info]   /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --new_master_host=192.168.0.60 --new_master_ip=192.168.0.60 --new_master_port=  
  157.  
  158. IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===
  159.  
  160. Enabling the VIP - 192.168.0.88 on the new master - 192.168.0.60
  161. Mon Apr  ::  - [info]  OK.
  162. Mon Apr  ::  - [info] Setting read_only= on 192.168.0.60(192.168.0.60:)..
  163. Mon Apr  ::  - [info]  ok.
  164. Mon Apr  ::  - [info] ** Finished master recovery successfully.
  165. Mon Apr  ::  - [info] * Phase : Master Recovery Phase completed.
  166. Mon Apr  ::  - [info]
  167. Mon Apr  ::  - [info] * Phase : Slaves Recovery Phase..
  168. Mon Apr  ::  - [info]
  169. Mon Apr  ::  - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
  170. Mon Apr  ::  - [info]
  171. Mon Apr  ::  - [info] -- Slave diff file generation on host 192.168.0.70(192.168.0.70:) started, pid: . Check tmp log /var/log/masterha/app1.log/192.168..70_3306_20140421201548.log if it takes time..
  172. Mon Apr  ::  - [info]
  173. Mon Apr  ::  - [info] Log messages from 192.168.0.70 ...
  174. Mon Apr  ::  - [info]
  175. Mon Apr  ::  - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
  176. Mon Apr  ::  - [info] End of log messages from 192.168.0.70.
  177. Mon Apr  ::  - [info] -- 192.168.0.70(192.168.0.70:) has the latest relay log events.
  178. Mon Apr  ::  - [info] Generating relay diff files from the latest slave succeeded.
  179. Mon Apr  ::  - [info]
  180. Mon Apr  ::  - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
  181. Mon Apr  ::  - [info]
  182. Mon Apr  ::  - [info] -- Slave recovery on host 192.168.0.70(192.168.0.70:) started, pid: . Check tmp log /var/log/masterha/app1.log/192.168..70_3306_20140421201548.log if it takes time..
  183. Mon Apr  ::  - [info]
  184. Mon Apr  ::  - [info] Log messages from 192.168.0.70 ...
  185. Mon Apr  ::  - [info]
  186. Mon Apr  ::  - [info] Sending binlog..
  187. Mon Apr  ::  - [info] scp from local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog to root@192.168.0.70:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog succeeded.
  188. Mon Apr  ::  - [info] Starting recovery on 192.168.0.70(192.168.0.70:)..
  189. Mon Apr  ::  - [info]  Generating diffs succeeded.
  190. Mon Apr  ::  - [info] Waiting until all relay logs are applied.
  191. Mon Apr  ::  - [info]  done.
  192. Mon Apr  ::  - [info] Getting slave status..
  193. Mon Apr  ::  - [info] This slave(192.168.0.70)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000018:112). No need to recover from Exec_Master_Log_Pos.
  194. Mon Apr  ::  - [info] Connecting to the target slave host 192.168.0.70, running recover script..
  195. Mon Apr  ::  - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user=root --slave_host=192.168.0.70 --slave_ip=192.168.0.70  --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog --workdir=/tmp --target_version=5.5.-ndb-7.2.-gpl-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.53 --slave_pass=xxx
  196. Mon Apr  ::  - [info]
  197. Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421201548.binlog on 192.168.0.70:. This may take long time...
  198. Applying log files succeeded.
  199. Mon Apr  ::  - [info]  All relay logs were successfully applied.
  200. Mon Apr  ::  - [info]  Resetting slave 192.168.0.70(192.168.0.70:) and starting replication from the new master 192.168.0.60(192.168.0.60:)..
  201. Mon Apr  ::  - [info]  Executed CHANGE MASTER.
  202. Mon Apr  ::  - [info]  Slave started.
  203. Mon Apr  ::  - [info] End of log messages from 192.168.0.70.
  204. Mon Apr  ::  - [info] -- Slave recovery on host 192.168.0.70(192.168.0.70:) succeeded.
  205. Mon Apr  ::  - [info] All new slave servers recovered successfully.
  206. Mon Apr  ::  - [info]
  207. Mon Apr  ::  - [info] * Phase : New master cleanup phease..
  208. Mon Apr  ::  - [info]
  209. Mon Apr  ::  - [info] Resetting slave info on the new master..
  210. Mon Apr  ::  - [info]  192.168.0.60: Resetting slave info succeeded.
  211. Mon Apr  ::  - [info] Master failover to 192.168.0.60(192.168.0.60:) completed successfully.
  212. Mon Apr  ::  - [info] Deleted server1 entry from /etc/masterha/app1.cnf .
  213. Mon Apr  ::  - [info] 
  214.  
  215. ----- Failover Report -----
  216.  
  217. app1: MySQL Master failover 192.168.0.50 to 192.168.0.60 succeeded
  218.  
  219. Master 192.168.0.50 is down!
  220.  
  221. Check MHA Manager logs at server01:/var/log/masterha/app1/manager.log for details.
  222.  
  223. Started automated(non-interactive) failover.
  224. Invalidated master IP address on 192.168.0.50.
  225. The latest slave 192.168.0.60(192.168.0.60:) has all relay logs for recovery.
  226. Selected 192.168.0.60 as a new master.
  227. 192.168.0.60: OK: Applying all logs succeeded.
  228. 192.168.0.60: OK: Activated master IP address.
  229. 192.168.0.70: This host has the latest relay log events.
  230. Generating relay diff files from the latest slave succeeded.
  231. 192.168.0.70: OK: Applying all logs succeeded. Slave started, replicating from 192.168.0.60.
  232. 192.168.0.60: Resetting slave info succeeded.
  233. Master failover to 192.168.0.60(192.168.0.60:) completed successfully.
  234. [root@192.168.0.20 ~]#

看到最后的Master failover to 192.168.0.60(192.168.0.60:3306) completed successfully.说明备选master现在已经上位了。

从上面的输出可以看出整个MHA的切换过程，共包括以下的步骤：

1.配置文件检查阶段，这个阶段会检查整个集群配置文件配置

2.宕机的master处理，这个阶段包括虚拟ip摘除操作，主机关机操作（这个我这里还没有实现，需要研究）

3.复制dead maste和最新slave相差的relay log，并保存到MHA Manger具体的目录下

4.识别含有最新更新的slave

5.应用从master保存的二进制日志事件（binlog events）

6.提升一个slave为新的master进行复制

7.使其他的slave连接新的master进行复制

最后启动MHA Manger监控，查看集群里面现在谁是master（在切换后监控就停止了。。。还有东西没搞对？）后来在官方网站看到这句话就明白了 。

Running MHA Manager from daemontools

Currently MHA Manager process does not run as a daemon. If failover completed successfully or the master process was killed by accident, the manager stops working. To run as a daemon, daemontool. or any external daemon program can be used. Here is an example to run from daemontools.

  1. [root@192.168.0.20 ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
  2. app1 (pid:) is running(:PING_OK), master:192.168.0.60
  3. [root@192.168.0.20 ~]#

二.手动Failover（MHA Manager必须没有运行）

手动failover，这种场景意味着在业务上没有启用MHA自动切换功能，当主服务器故障时，人工手动调用MHA来进行故障切换操作，具体命令如下：

注意：如果，MHA manager检测到没有dead的server，将报错，并结束failover： 

  1. Mon Apr  ::  - [info] Dead Servers:
  2. Mon Apr  ::  - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln181] None of server is dead. Stop failover.
  3. Mon Apr  ::  - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln178] Got ERROR:  at /usr/local/bin/masterha_master_switch line

进行手动切换命令如下：

  1. [root@192.168.0.20 ~]# masterha_master_switch --master_state=dead --conf=/etc/masterha/app1.cnf --dead_master_host=192.168.0.50 --dead_master_port= --new_master_host=192.168.0.60 --new_master_port= --ignore_last_failover

输出的信息会询问你是否进行切换：

  1. Mon Apr  ::  - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  2. Mon Apr  ::  - [info] Reading application default configurations from /etc/masterha/app1.cnf..
  3. Mon Apr  ::  - [info] Reading server configurations from /etc/masterha/app1.cnf..
  4. Mon Apr  ::  - [info] MHA::MasterFailover version 0.53.
  5. Mon Apr  ::  - [info] Starting master failover.
  6. Mon Apr  ::  - [info]
  7. Mon Apr  ::  - [info] * Phase : Configuration Check Phase..
  8. Mon Apr  ::  - [info]
  9. Mon Apr  ::  - [info] Dead Servers:
  10. Mon Apr  ::  - [info]   192.168.0.50(192.168.0.50:)
  11. Mon Apr  ::  - [info] Checking master reachability via mysql(double check)..
  12. Mon Apr  ::  - [info]  ok.
  13. Mon Apr  ::  - [info] Alive Servers:
  14. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)
  15. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)
  16. Mon Apr  ::  - [info] Alive Slaves:
  17. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  18. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  19. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  20. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  21. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  22. Master 192.168.0.50 is dead. Proceed? (yes/NO): yes
  23. Mon Apr  ::  - [info] ** Phase : Configuration Check Phase completed.
  24. Mon Apr  ::  - [info]
  25. Mon Apr  ::  - [info] * Phase : Dead Master Shutdown Phase..
  26. Mon Apr  ::  - [info]
  27. Mon Apr  ::  - [info] HealthCheck: SSH to 192.168.0.50 is reachable.
  28. Mon Apr  ::  - [info] Forcing shutdown so that applications never connect to the current master..
  29. Mon Apr  ::  - [info] Executing master IP deactivatation script:
  30. Mon Apr  ::  - [info]   /usr/local/bin/master_ip_failover --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --command=stopssh --ssh_user=root  
  31.  
  32. IN SCRIPT TEST====/sbin/ifconfig eth1: down==/sbin/ifconfig eth1: 192.168.0.88/===
  33.  
  34. Disabling the VIP on old master: 192.168.0.50
  35. Mon Apr  ::  - [info]  done.
  36. Mon Apr  ::  - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
  37. Mon Apr  ::  - [info] * Phase : Dead Master Shutdown Phase completed.
  38. Mon Apr  ::  - [info]
  39. Mon Apr  ::  - [info] * Phase : Master Recovery Phase..
  40. Mon Apr  ::  - [info]
  41. Mon Apr  ::  - [info] * Phase 3.1: Getting Latest Slaves Phase..
  42. Mon Apr  ::  - [info]
  43. Mon Apr  ::  - [info] The latest binary log file/position on all slaves is mysql-bin.:
  44. Mon Apr  ::  - [info] Latest slaves (Slaves that received relay log files to the latest):
  45. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  46. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  47. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  48. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  49. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  50. Mon Apr  ::  - [info] The oldest binary log file/position on all slaves is mysql-bin.:
  51. Mon Apr  ::  - [info] Oldest slaves:
  52. Mon Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  53. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  54. Mon Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  55. Mon Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  56. Mon Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  57. Mon Apr  ::  - [info]
  58. Mon Apr  ::  - [info] * Phase 3.2: Saving Dead Master's Binlog Phase..
  59. Mon Apr  ::  - [info]
  60. Mon Apr  ::  - [info] Fetching dead master's binary logs..
  61. Mon Apr  ::  - [info] Executing command on the dead master 192.168.0.50(192.168.0.50:): save_binary_logs --command=save --start_file=mysql-bin.  --start_pos= --binlog_dir=/data/mysql --output_file=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog --handle_raw_binlog= --disable_log_bin= --manager_version=0.53
  62.   Creating /tmp if not exists..    ok.
  63.  Concat binary/relay logs from mysql-bin. pos  to mysql-bin. EOF into /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog ..
  64.   Dumping binlog format description event, from position  to .. ok.
  65.   Dumping effective binlog data from /data/mysql/mysql-bin. position  to tail().. ok.
  66.  Concat succeeded.
  67. saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog                                                   %       .1KB/s   :
  68. Mon Apr  ::  - [info] scp from root@192.168.0.50:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog to local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog succeeded.
  69. Mon Apr  ::  - [info] HealthCheck: SSH to 192.168.0.60 is reachable.
  70. Mon Apr  ::  - [info] HealthCheck: SSH to 192.168.0.70 is reachable.
  71. Mon Apr  ::  - [info]
  72. Mon Apr  ::  - [info] * Phase 3.3: Determining New Master Phase..
  73. Mon Apr  ::  - [info]
  74. Mon Apr  ::  - [info] Finding the latest slave that has all relay logs for recovering other slaves..
  75. Mon Apr  ::  - [info] All slaves received relay logs to the same position. No need to resync each other.
  76. Mon Apr  ::  - [info] 192.168.0.60 can be new master.
  77. Mon Apr  ::  - [info] New master is 192.168.0.60(192.168.0.60:)
  78. Mon Apr  ::  - [info] Starting master failover..
  79. Mon Apr  ::  - [info]
  80. From:
  81. 192.168.0.50 (current master)
  82.  +--192.168.0.60
  83.  +--192.168.0.70
  84.  
  85. To:
  86. 192.168.0.60 (new master)
  87.  +--192.168.0.70
  88.  
  89. Starting master switch from 192.168.0.50(192.168.0.50:) to 192.168.0.60(192.168.0.60:)? (yes/NO): yes
  90. Mon Apr  ::  - [info] New master decided manually is 192.168.0.60(192.168.0.60:)
  91. Mon Apr  ::  - [info]
  92. Mon Apr  ::  - [info] * Phase 3.3: New Master Diff Log Generation Phase..
  93. Mon Apr  ::  - [info]
  94. Mon Apr  ::  - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
  95. Mon Apr  ::  - [info] Sending binlog..
  96. saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog                                                   %       .1KB/s   :
  97. Mon Apr  ::  - [info] scp from local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog to root@192.168.0.60:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog succeeded.
  98. Mon Apr  ::  - [info]
  99. Mon Apr  ::  - [info] * Phase 3.4: Master Log Apply Phase..
  100. Mon Apr  ::  - [info]
  101. Mon Apr  ::  - [info] *NOTICE: If any error happens from this phase, manual recovery is needed.
  102. Mon Apr  ::  - [info] Starting recovery on 192.168.0.60(192.168.0.60:)..
  103. Mon Apr  ::  - [info]  Generating diffs succeeded.
  104. Mon Apr  ::  - [info] Waiting until all relay logs are applied.
  105. Mon Apr  ::  - [info]  done.
  106. Mon Apr  ::  - [info] Getting slave status..
  107. Mon Apr  ::  - [info] This slave(192.168.0.60)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000020:112). No need to recover from Exec_Master_Log_Pos.
  108. Mon Apr  ::  - [info] Connecting to the target slave host 192.168.0.60, running recover script..
  109. Mon Apr  ::  - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user=root --slave_host=192.168.0.60 --slave_ip=192.168.0.60  --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog --workdir=/tmp --target_version=5.5.-ndb-7.2.-gpl-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.53 --slave_pass=xxx
  110. Mon Apr  ::  - [info]
  111. Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog on 192.168.0.60:. This may take long time...
  112. Applying log files succeeded.
  113. Mon Apr  ::  - [info]  All relay logs were successfully applied.
  114. Mon Apr  ::  - [info] Getting new master's binlog name and position..
  115. Mon Apr  ::  - [info]  mysql-bin.:
  116. Mon Apr  ::  - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.0.60', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000022', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
  117. Mon Apr  ::  - [info] Executing master IP activate script:
  118. Mon Apr  ::  - [info]   /usr/local/bin/master_ip_failover --command=start --ssh_user=root --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --new_master_host=192.168.0.60 --new_master_ip=192.168.0.60 --new_master_port=  
  119.  
  120. IN SCRIPT TEST====/sbin/ifconfig eth1: down==/sbin/ifconfig eth1: 192.168.0.88/===
  121.  
  122. Enabling the VIP - 192.168.0.88/ on the new master - 192.168.0.60
  123. Mon Apr  ::  - [info]  OK.
  124. Mon Apr  ::  - [info] Setting read_only= on 192.168.0.60(192.168.0.60:)..
  125. Mon Apr  ::  - [info]  ok.
  126. Mon Apr  ::  - [info] ** Finished master recovery successfully.
  127. Mon Apr  ::  - [info] * Phase : Master Recovery Phase completed.
  128. Mon Apr  ::  - [info]
  129. Mon Apr  ::  - [info] * Phase : Slaves Recovery Phase..
  130. Mon Apr  ::  - [info]
  131. Mon Apr  ::  - [info] * Phase 4.1: Starting Parallel Slave Diff Log Generation Phase..
  132. Mon Apr  ::  - [info]
  133. Mon Apr  ::  - [info] -- Slave diff file generation on host 192.168.0.70(192.168.0.70:) started, pid: . Check tmp log /var/log/masterha/app1.log/192.168..70_3306_20140421212800.log if it takes time..
  134. Mon Apr  ::  - [info]
  135. Mon Apr  ::  - [info] Log messages from 192.168.0.70 ...
  136. Mon Apr  ::  - [info]
  137. Mon Apr  ::  - [info]  This server has all relay logs. No need to generate diff files from the latest slave.
  138. Mon Apr  ::  - [info] End of log messages from 192.168.0.70.
  139. Mon Apr  ::  - [info] -- 192.168.0.70(192.168.0.70:) has the latest relay log events.
  140. Mon Apr  ::  - [info] Generating relay diff files from the latest slave succeeded.
  141. Mon Apr  ::  - [info]
  142. Mon Apr  ::  - [info] * Phase 4.2: Starting Parallel Slave Log Apply Phase..
  143. Mon Apr  ::  - [info]
  144. Mon Apr  ::  - [info] -- Slave recovery on host 192.168.0.70(192.168.0.70:) started, pid: . Check tmp log /var/log/masterha/app1.log/192.168..70_3306_20140421212800.log if it takes time..
  145. saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog                                                   %       .1KB/s   :
  146. Mon Apr  ::  - [info]
  147. Mon Apr  ::  - [info] Log messages from 192.168.0.70 ...
  148. Mon Apr  ::  - [info]
  149. Mon Apr  ::  - [info] Sending binlog..
  150. Mon Apr  ::  - [info] scp from local:/var/log/masterha/app1.log/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog to root@192.168.0.70:/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog succeeded.
  151. Mon Apr  ::  - [info] Starting recovery on 192.168.0.70(192.168.0.70:)..
  152. Mon Apr  ::  - [info]  Generating diffs succeeded.
  153. Mon Apr  ::  - [info] Waiting until all relay logs are applied.
  154. Mon Apr  ::  - [info]  done.
  155. Mon Apr  ::  - [info] Getting slave status..
  156. Mon Apr  ::  - [info] This slave(192.168.0.70)'s Exec_Master_Log_Pos equals to Read_Master_Log_Pos(mysql-bin.000020:112). No need to recover from Exec_Master_Log_Pos.
  157. Mon Apr  ::  - [info] Connecting to the target slave host 192.168.0.70, running recover script..
  158. Mon Apr  ::  - [info] Executing command: apply_diff_relay_logs --command=apply --slave_user=root --slave_host=192.168.0.70 --slave_ip=192.168.0.70  --slave_port= --apply_files=/tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog --workdir=/tmp --target_version=5.5.-ndb-7.2.-gpl-log --timestamp= --handle_raw_binlog= --disable_log_bin= --manager_version=0.53 --slave_pass=xxx
  159. Mon Apr  ::  - [info]
  160. Applying differential binary/relay log files /tmp/saved_master_binlog_from_192.168.0.50_3306_20140421212800.binlog on 192.168.0.70:. This may take long time...
  161. Applying log files succeeded.
  162. Mon Apr  ::  - [info]  All relay logs were successfully applied.
  163. Mon Apr  ::  - [info]  Resetting slave 192.168.0.70(192.168.0.70:) and starting replication from the new master 192.168.0.60(192.168.0.60:)..
  164. Mon Apr  ::  - [info]  Executed CHANGE MASTER.
  165. Mon Apr  ::  - [info]  Slave started.
  166. Mon Apr  ::  - [info] End of log messages from 192.168.0.70.
  167. Mon Apr  ::  - [info] -- Slave recovery on host 192.168.0.70(192.168.0.70:) succeeded.
  168. Mon Apr  ::  - [info] All new slave servers recovered successfully.
  169. Mon Apr  ::  - [info]
  170. Mon Apr  ::  - [info] * Phase : New master cleanup phease..
  171. Mon Apr  ::  - [info]
  172. Mon Apr  ::  - [info] Resetting slave info on the new master..
  173. Mon Apr  ::  - [info]  192.168.0.60: Resetting slave info succeeded.
  174. Mon Apr  ::  - [info] Master failover to 192.168.0.60(192.168.0.60:) completed successfully.
  175. Mon Apr  ::  - [info] 
  176.  
  177. ----- Failover Report -----
  178.  
  179. app1: MySQL Master failover 192.168.0.50 to 192.168.0.60 succeeded
  180.  
  181. Master 192.168.0.50 is down!
  182.  
  183. Check MHA Manager logs at server01 for details.
  184.  
  185. Started manual(interactive) failover.
  186. Invalidated master IP address on 192.168.0.50.
  187. The latest slave 192.168.0.60(192.168.0.60:) has all relay logs for recovery.
  188. Selected 192.168.0.60 as a new master.
  189. 192.168.0.60: OK: Applying all logs succeeded.
  190. 192.168.0.60: OK: Activated master IP address.
  191. 192.168.0.70: This host has the latest relay log events.
  192. Generating relay diff files from the latest slave succeeded.
  193. 192.168.0.70: OK: Applying all logs succeeded. Slave started, replicating from 192.168.0.60.
  194. 192.168.0.60: Resetting slave info succeeded.
  195. Master failover to 192.168.0.60(192.168.0.60:) completed successfully.

上述模拟了master宕机的情况下手动把192.168.0.60提升为主库的操作过程。

三.在线进行切换

在许多情况下， 需要将现有的主服务器迁移到另外一台服务器上。 比如主服务器硬件故障，RAID 控制卡需要重建，将主服务器移到性能更好的服务器上等等。维护主服务器引起性能下降， 导致停机时间至少无法写入数据。 另外， 阻塞或杀掉当前运行的会话会导致主主之间数据不一致的问题发生。 MHA 提供快速切换和优雅的阻塞写入，这个切换过程只需要 0.5-2s 的时间，这段时间内数据是无法写入的。在很多情况下，0.5-2s 的阻塞写入是可以接受的。因此切换主服务器不需要计划分配维护时间窗口。

MHA在线切换的大概过程：
1.检测复制设置和确定当前主服务器
2.确定新的主服务器
3.阻塞写入到当前主服务器
4.等待所有从服务器赶上复制
5.授予写入到新的主服务器
6.重新设置从服务器

注意，在线切换的时候应用架构需要考虑以下两个问题：

1.自动识别master和slave的问题（master的机器可能会切换），如果采用了vip的方式，基本可以解决这个问题。

2.负载均衡的问题（可以定义大概的读写比例，每台机器可承担的负载比例，当有机器离开集群时，需要考虑这个问题）

为了保证数据完全一致性，在最快的时间内完成切换，MHA的在线切换必须满足以下条件才会切换成功，否则会切换失败。

1.所有slave的IO线程都在运行

2.所有slave的SQL线程都在运行

3.所有的show slave status的输出中Seconds_Behind_Master参数小于或者等于running_updates_limit秒，如果在切换过程中不指定running_updates_limit,那么默认情况下running_updates_limit为1秒。

4.在master端，通过show processlist输出，没有一个更新花费的时间大于running_updates_limit秒。

在线切换步骤如下：

首先，停掉MHA监控：

  1. [root@192.168.0.20 ~]# masterha_stop --conf=/etc/masterha/app1.cnf

其次，进行在线切换操作（模拟在线切换主库操作，原主库192.168.0.50变为slave，192.168.0.60提升为新的主库）

  1. [root@192.168.0.20 ~]# masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.0.60 --new_master_port= --orig_master_is_new_slave --running_updates_limit=

最后查看日志，了解切换过程，输出信息如下：

  1. [root@192.168.0.20 ~]#  masterha_master_switch --conf=/etc/masterha/app1.cnf --master_state=alive --new_master_host=192.168.0.60 --new_master_port= --orig_master_is_new_slave --running_updates_limit=
  2. Wed Apr  ::  - [info] MHA::MasterRotate version 0.53.
  3. Wed Apr  ::  - [info] Starting online master switch..
  4. Wed Apr  ::  - [info]
  5. Wed Apr  ::  - [info] * Phase : Configuration Check Phase..
  6. Wed Apr  ::  - [info]
  7. Wed Apr  ::  - [info] Reading default configuratoins from /etc/masterha_default.cnf..
  8. Wed Apr  ::  - [info] Reading application default configurations from /etc/masterha/app1.cnf..
  9. Wed Apr  ::  - [info] Reading server configurations from /etc/masterha/app1.cnf..
  10. Wed Apr  ::  - [info] Multi-master configuration is detected. Current primary(writable) master is 192.168.0.50(192.168.0.50:)
  11. Wed Apr  ::  - [info] Master configurations are as below:
  12. Master 192.168.0.60(192.168.0.60:), replicating from 192.168.0.50(192.168.0.50:), read-only
  13. Master 192.168.0.50(192.168.0.50:), replicating from 192.168.0.60(192.168.0.60:)
  14.  
  15. Wed Apr  ::  - [info] Current Alive Master: 192.168.0.50(192.168.0.50:)
  16. Wed Apr  ::  - [info] Alive Slaves:
  17. Wed Apr  ::  - [info]   192.168.0.60(192.168.0.60:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  18. Wed Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  19. Wed Apr  ::  - [info]     Primary candidate for the new Master (candidate_master is set)
  20. Wed Apr  ::  - [info]   192.168.0.70(192.168.0.70:)  Version=5.5.-ndb-7.2.-gpl-log (oldest major version between slaves) log-bin:enabled
  21. Wed Apr  ::  - [info]     Replicating from 192.168.0.50(192.168.0.50:)
  22.  
  23. It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.0.50(192.168.0.50:)? (YES/no): yes
  24. Wed Apr  ::  - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
  25. Wed Apr  ::  - [info]  ok.
  26. Wed Apr  ::  - [info] Checking MHA is not monitoring or doing failover..
  27. Wed Apr  ::  - [info] Checking replication health on 192.168.0.60..
  28. Wed Apr  ::  - [info]  ok.
  29. Wed Apr  ::  - [info] Checking replication health on 192.168.0.70..
  30. Wed Apr  ::  - [info]  ok.
  31. Wed Apr  ::  - [info] 192.168.0.60 can be new master.
  32. Wed Apr  ::  - [info]
  33. From:
  34. 192.168.0.50 (current master)
  35.  +--192.168.0.60
  36.  +--192.168.0.70
  37.  
  38. To:
  39. 192.168.0.60 (new master)
  40.  +--192.168.0.70
  41.  +--192.168.0.50
  42.  
  43. Starting master switch from 192.168.0.50(192.168.0.50:) to 192.168.0.60(192.168.0.60:)? (yes/NO): yes
  44. Wed Apr  ::  - [info] Checking whether 192.168.0.60(192.168.0.60:) is ok for the new master..
  45. Wed Apr  ::  - [info]  ok.
  46. Wed Apr  ::  - [info] ** Phase : Configuration Check Phase completed.
  47. Wed Apr  ::  - [info]
  48. Wed Apr  ::  - [info] * Phase : Rejecting updates Phase..
  49. Wed Apr  ::  - [info]
  50. Wed Apr  ::  - [info] Executing master ip online change script to disable write on the current master:
  51. Wed Apr  ::  - [info]   /usr/local/bin/master_ip_online_change.pl --command=stop --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --new_master_host=192.168.0.60 --new_master_ip=192.168.0.60 --new_master_port=
  52. Wed Apr  ::   Set read_only on the new master.. ok.
  53. Wed Apr  ::   Set read_only= on the orig master.. ok.
  54. Disabling the VIP on old master: 192.168.0.50
  55. reverse mapping checking getaddrinfo for bogon [192.168.0.50] failed - POSSIBLE BREAK-IN ATTEMPT!
  56. Wed Apr  ::   Killing all application threads..
  57. Wed Apr  ::   done.
  58. Wed Apr  ::  - [info]  ok.
  59. Wed Apr  ::  - [info] Locking all tables on the orig master to reject updates from everybody (including root):
  60. Wed Apr  ::  - [info] Executing FLUSH TABLES WITH READ LOCK..
  61. Wed Apr  ::  - [info]  ok.
  62. Wed Apr  ::  - [info] Orig master binlog:pos is mysql-bin.:.
  63. Wed Apr  ::  - [info]  Waiting to execute all relay logs on 192.168.0.60(192.168.0.60:)..
  64. Wed Apr  ::  - [info]  master_pos_wait(mysql-bin.:) completed on 192.168.0.60(192.168.0.60:). Executed  events.
  65. Wed Apr  ::  - [info]   done.
  66. Wed Apr  ::  - [info] Getting new master's binlog name and position..
  67. Wed Apr  ::  - [info]  mysql-bin.:
  68. Wed Apr  ::  - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.0.60', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000023', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
  69. Wed Apr  ::  - [info] Executing master ip online change script to allow write on the new master:
  70. Wed Apr  ::  - [info]   /usr/local/bin/master_ip_online_change.pl --command=start --orig_master_host=192.168.0.50 --orig_master_ip=192.168.0.50 --orig_master_port= --new_master_host=192.168.0.60 --new_master_ip=192.168.0.60 --new_master_port=
  71. Wed Apr  ::   Set read_only= on the new master.
  72. Enabling the VIP - 192.168.0.88/ on the new master - 192.168.0.60
  73. reverse mapping checking getaddrinfo for bogon [192.168.0.60] failed - POSSIBLE BREAK-IN ATTEMPT!
  74. Wed Apr  ::  - [info]  ok.
  75. Wed Apr  ::  - [info]
  76. Wed Apr  ::  - [info] * Switching slaves in parallel..
  77. Wed Apr  ::  - [info]
  78. Wed Apr  ::  - [info] -- Slave switch on host 192.168.0.70(192.168.0.70:) started, pid:
  79. Wed Apr  ::  - [info]
  80. Wed Apr  ::  - [info] Log messages from 192.168.0.70 ...
  81. Wed Apr  ::  - [info]
  82. Wed Apr  ::  - [info]  Waiting to execute all relay logs on 192.168.0.70(192.168.0.70:)..
  83. Wed Apr  ::  - [info]  master_pos_wait(mysql-bin.:) completed on 192.168.0.70(192.168.0.70:). Executed  events.
  84. Wed Apr  ::  - [info]   done.
  85. Wed Apr  ::  - [info]  Resetting slave 192.168.0.70(192.168.0.70:) and starting replication from the new master 192.168.0.60(192.168.0.60:)..
  86. Wed Apr  ::  - [info]  Executed CHANGE MASTER.
  87. Wed Apr  ::  - [info]  Slave started.
  88. Wed Apr  ::  - [info] End of log messages from 192.168.0.70 ...
  89. Wed Apr  ::  - [info]
  90. Wed Apr  ::  - [info] -- Slave switch on host 192.168.0.70(192.168.0.70:) succeeded.
  91. Wed Apr  ::  - [info] Unlocking all tables on the orig master:
  92. Wed Apr  ::  - [info] Executing UNLOCK TABLES..
  93. Wed Apr  ::  - [info]  ok.
  94. Wed Apr  ::  - [info] Starting orig master as a new slave..
  95. Wed Apr  ::  - [info]  Resetting slave 192.168.0.50(192.168.0.50:) and starting replication from the new master 192.168.0.60(192.168.0.60:)..
  96. Wed Apr  ::  - [info]  Executed CHANGE MASTER.
  97. Wed Apr  ::  - [info]  Slave started.
  98. Wed Apr  ::  - [info] All new slave servers switched successfully.
  99. Wed Apr  ::  - [info]
  100. Wed Apr  ::  - [info] * Phase : New master cleanup phease..
  101. Wed Apr  ::  - [info]
  102. Wed Apr  ::  - [info]  192.168.0.60: Resetting slave info succeeded.
  103. Wed Apr  ::  - [info] Switching master to 192.168.0.60(192.168.0.60:) completed successfully.

其中参数的意思：

--orig_master_is_new_slave 切换时加上此参数是将原 master 变为 slave 节点，如果不加此参数，原来的 master 将不启动

--running_updates_limit=10000,故障切换时,候选master 如果有延迟的话， mha 切换不能成功，加上此参数表示延迟在此时间范围内都可切换（单位为s），但是切换的时间长短是由recover 时relay 日志的大小决定

注意：由于在线进行切换需要调用到master_ip_online_change这个脚本，但是由于该脚本不完整，需要自己进行相应的修改，我google到后发现还是有问题，脚本中new_master_password这个变量获取不到，导致在线切换失败，所以进行了相关的硬编码，直接把mysql的root用户密码赋值给变量new_master_password，如果有哪位大牛知道原因，请指点指点。这个脚本还可以管理vip。下面贴出脚本：

  1. #!/usr/bin/env perl
  2.  
  3. #  Copyright (C) 2011 DeNA Co.,Ltd.
  4. #
  5. #  This program is free software; you can redistribute it and/or modify
  6. #  it under the terms of the GNU General Public License as published by
  7. #  the Free Software Foundation; either version 2 of the License, or
  8. #  (at your option) any later version.
  9. #
  10. #  This program is distributed in the hope that it will be useful,
  11. #  but WITHOUT ANY WARRANTY; without even the implied warranty of
  12. #  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  13. #  GNU General Public License for more details.
  14. #
  15. #  You should have received a copy of the GNU General Public License
  16. #   along with this program; if not, write to the Free Software
  17. #  Foundation, Inc.,
  18. #  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
  19.  
  20. ## Note: This is a sample script and is not complete. Modify the script based on your environment.
  21.  
  22. use strict;
  23. use warnings FATAL => 'all';
  24.  
  25. use Getopt::Long;
  26. use MHA::DBHelper;
  27. use MHA::NodeUtil;
  28. use Time::HiRes qw( sleep gettimeofday tv_interval );
  29. use Data::Dumper;
  30.  
  31. my $_tstart;
  32. my $_running_interval = 0.1;
  33. my (
  34.   $command,          $orig_master_host, $orig_master_ip,
  35.   $orig_master_port, $orig_master_user,
  36.   $new_master_host,  $new_master_ip,    $new_master_port,
  37.   $new_master_user,
  38. );
  39.  
  40. my $vip = '192.168.0.88/24';  # Virtual IP
  41. my $key = "1";
  42. my $ssh_start_vip = "/sbin/ifconfig eth1:$key $vip";
  43. my $ssh_stop_vip = "/sbin/ifconfig eth1:$key down";
  44. my $ssh_user = "root";
  45. my $new_master_password='123456';
  46. my $orig_master_password='123456';
  47. GetOptions(
  48.   'command=s'              => \$command,
  49.   #'ssh_user=s'             => \$ssh_user,
  50.   'orig_master_host=s'     => \$orig_master_host,
  51.   'orig_master_ip=s'       => \$orig_master_ip,
  52.   'orig_master_port=i'     => \$orig_master_port,
  53.   'orig_master_user=s'     => \$orig_master_user,
  54.   #'orig_master_password=s' => \$orig_master_password,
  55.   'new_master_host=s'      => \$new_master_host,
  56.   'new_master_ip=s'        => \$new_master_ip,
  57.   'new_master_port=i'      => \$new_master_port,
  58.   'new_master_user=s'      => \$new_master_user,
  59.   #'new_master_password=s'  => \$new_master_password,
  60. );
  61.  
  62. exit &main();
  63.  
  64. sub current_time_us {
  65.   my ( $sec, $microsec ) = gettimeofday();
  66.   my $curdate = localtime($sec);
  67.   return $curdate . " " . sprintf( "%06d", $microsec );
  68. }
  69.  
  70. sub sleep_until {
  71.   my $elapsed = tv_interval($_tstart);
  72.   if ( $_running_interval > $elapsed ) {
  73.     sleep( $_running_interval - $elapsed );
  74.   }
  75. }
  76.  
  77. sub get_threads_util {
  78.   my $dbh                    = shift;
  79.   my $my_connection_id       = shift;
  80.   my $running_time_threshold = shift;
  81.   my $type                   = shift;
  82.   $running_time_threshold =  unless ($running_time_threshold);
  83.   $type                   =  unless ($type);
  84.   my @threads;
  85.  
  86.   my $sth = $dbh->prepare("SHOW PROCESSLIST");
  87.   $sth->execute();
  88.  
  89.   while ( my $ref = $sth->fetchrow_hashref() ) {
  90.     my $id         = $ref->{Id};
  91.     my $user       = $ref->{User};
  92.     my $host       = $ref->{Host};
  93.     my $command    = $ref->{Command};
  94.     my $state      = $ref->{State};
  95.     my $query_time = $ref->{Time};
  96.     my $info       = $ref->{Info};
  97.     $info =~ s/^\s*(.*?)\s*$/$/ if defined($info);
  98.     next if ( $my_connection_id == $id );
  99.     next if ( defined($query_time) && $query_time < $running_time_threshold );
  100.     next if ( defined($command)    && $command eq "Binlog Dump" );
  101.     next if ( defined($user)       && $user eq "system user" );
  102.     next
  103.       if ( defined($command)
  104.       && $command eq "Sleep"
  105.       && defined($query_time)
  106.       && $query_time >=  );
  107.  
  108.     if ( $type >=  ) {
  109.       next if ( defined($command) && $command eq "Sleep" );
  110.       next if ( defined($command) && $command eq "Connect" );
  111.     }
  112.  
  113.     if ( $type >=  ) {
  114.       next if ( defined($info) && $info =~ m/^select/i );
  115.       next if ( defined($info) && $info =~ m/^show/i );
  116.     }
  117.  
  118.     push @threads, $ref;
  119.   }
  120.   return @threads;
  121. }
  122.  
  123. sub main {
  124.   if ( $command eq "stop" ) {
  125.     ## Gracefully killing connections on the current master
  126.     # 1. Set read_only= 1 on the new master
  127.     # 2. DROP USER so that no app user can establish new connections
  128.     # 3. Set read_only= 1 on the current master
  129.     # 4. Kill current queries
  130.     # * Any database access failure will result in script die.
  131.     my $exit_code = ;
  132.     eval {
  133.       ## Setting read_only=1 on the new master (to avoid accident)
  134.       my $new_master_handler = new MHA::DBHelper();
  135.  
  136.       # args: hostname, port, user, password, raise_error(die_on_error)_or_not
  137.       $new_master_handler->connect( $new_master_ip, $new_master_port,
  138.         $new_master_user, $new_master_password,  );
  139.       print current_time_us() . " Set read_only on the new master.. ";
  140.       $new_master_handler->enable_read_only();
  141.       if ( $new_master_handler->is_read_only() ) {
  142.         print "ok.\n";
  143.       }
  144.       else {
  145.         die "Failed!\n";
  146.       }
  147.       $new_master_handler->disconnect();
  148.  
  149.       # Connecting to the orig master, die if any database error happens
  150.       my $orig_master_handler = new MHA::DBHelper();
  151.       $orig_master_handler->connect( $orig_master_ip, $orig_master_port,
  152.         $orig_master_user, $orig_master_password,  );
  153.  
  154.       ## Drop application user so that nobody can connect. Disabling per-session binlog beforehand
  155.       #$orig_master_handler->disable_log_bin_local();
  156.       #print current_time_us() . " Drpping app user on the orig master..\n";
  157.       #FIXME_xxx_drop_app_user($orig_master_handler);
  158.  
  159.       ## Waiting for N * 100 milliseconds so that current connections can exit
  160.       my $time_until_read_only = ;
  161.       $_tstart = [gettimeofday];
  162.       my @threads = get_threads_util( $orig_master_handler->{dbh},
  163.         $orig_master_handler->{connection_id} );
  164.       while ( $time_until_read_only >  && $#threads >= 0 ) {
  165.         if ( $time_until_read_only %  ==  ) {
  166.           printf
  167. "%s Waiting all running %d threads are disconnected.. (max %d milliseconds)\n",
  168.             current_time_us(), $#threads + 1, $time_until_read_only * 100;
  169.           if ( $#threads < 5 ) {
  170.             print Data::Dumper->new( [$_] )->Indent()->Terse()->Dump . "\n"
  171.               foreach (@threads);
  172.           }
  173.         }
  174.         sleep_until();
  175.         $_tstart = [gettimeofday];
  176.         $time_until_read_only--;
  177.         @threads = get_threads_util( $orig_master_handler->{dbh},
  178.           $orig_master_handler->{connection_id} );
  179.       }
  180.  
  181.       ## Setting read_only=1 on the current master so that nobody(except SUPER) can write
  182.       print current_time_us() . " Set read_only=1 on the orig master.. ";
  183.       $orig_master_handler->enable_read_only();
  184.       if ( $orig_master_handler->is_read_only() ) {
  185.         print "ok.\n";
  186.       }
  187.       else {
  188.         die "Failed!\n";
  189.       }
  190.  
  191.       ## Waiting for M * 100 milliseconds so that current update queries can complete
  192.       my $time_until_kill_threads = ;
  193.       @threads = get_threads_util( $orig_master_handler->{dbh},
  194.         $orig_master_handler->{connection_id} );
  195.       while ( $time_until_kill_threads >  && $#threads >= 0 ) {
  196.         if ( $time_until_kill_threads %  ==  ) {
  197.           printf
  198. "%s Waiting all running %d queries are disconnected.. (max %d milliseconds)\n",
  199.             current_time_us(), $#threads + 1, $time_until_kill_threads * 100;
  200.           if ( $#threads < 5 ) {
  201.             print Data::Dumper->new( [$_] )->Indent()->Terse()->Dump . "\n"
  202.               foreach (@threads);
  203.           }
  204.         }
  205.         sleep_until();
  206.         $_tstart = [gettimeofday];
  207.         $time_until_kill_threads--;
  208.         @threads = get_threads_util( $orig_master_handler->{dbh},
  209.           $orig_master_handler->{connection_id} );
  210.       }
  211.  
  212.                 print "Disabling the VIP on old master: $orig_master_host \n";
  213.                 &stop_vip();     
  214.  
  215.       ## Terminating all threads
  216.       print current_time_us() . " Killing all application threads..\n";
  217.       $orig_master_handler->kill_threads(@threads) if ( $#threads >= 0 );
  218.       print current_time_us() . " done.\n";
  219.       #$orig_master_handler->enable_log_bin_local();
  220.       $orig_master_handler->disconnect();
  221.  
  222.       ## After finishing the script, MHA executes FLUSH TABLES WITH READ LOCK
  223.       $exit_code = ;
  224.     };
  225.     if ($@) {
  226.       warn "Got Error: $@\n";
  227.       exit $exit_code;
  228.     }
  229.     exit $exit_code;
  230.   }
  231.   elsif ( $command eq "start" ) {
  232.     ## Activating master ip on the new master
  233.     # 1. Create app user with write privileges
  234.     # 2. Moving backup script if needed
  235.     # 3. Register new master's ip to the catalog database
  236.  
  237. # We don't return error even though activating updatable accounts/ip failed so that we don't interrupt slaves' recovery.
  238. # If exit code is 0 or 10, MHA does not abort
  239.     my $exit_code = ;
  240.     eval {
  241.       my $new_master_handler = new MHA::DBHelper();
  242.  
  243.       # args: hostname, port, user, password, raise_error_or_not
  244.       $new_master_handler->connect( $new_master_ip, $new_master_port,
  245.         $new_master_user, $new_master_password,  );
  246.  
  247.       ## Set read_only=0 on the new master
  248.       #$new_master_handler->disable_log_bin_local();
  249.       print current_time_us() . " Set read_only=0 on the new master.\n";
  250.       $new_master_handler->disable_read_only();
  251.  
  252.       ## Creating an app user on the new master
  253.       #print current_time_us() . " Creating app user on the new master..\n";
  254.       #FIXME_xxx_create_app_user($new_master_handler);
  255.       #$new_master_handler->enable_log_bin_local();
  256.       $new_master_handler->disconnect();
  257.  
  258.       ## Update master ip on the catalog database, etc
  259.                 print "Enabling the VIP - $vip on the new master - $new_master_host \n";
  260.                 &start_vip();
  261.                 $exit_code = ;
  262.     };
  263.     if ($@) {
  264.       warn "Got Error: $@\n";
  265.       exit $exit_code;
  266.     }
  267.     exit $exit_code;
  268.   }
  269.   elsif ( $command eq "status" ) {
  270.  
  271.     # do nothing
  272.     exit ;
  273.   }
  274.   else {
  275.     &usage();
  276.     exit ;
  277.   }
  278. }
  279.  
  280. # A simple system call that enable the VIP on the new master
  281. sub start_vip() {
  282.     `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
  283. }
  284. # A simple system call that disable the VIP on the old_master
  285. sub stop_vip() {
  286.     `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
  287. }
  288.  
  289. sub usage {
  290.   print
  291. "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\n";
  292.   die;
  293. }

四.修复宕机的Master 

通常情况下自动切换以后，原master可能已经废弃掉，待原master主机修复后，如果数据完整的情况下，可能想把原来master重新作为新主库的slave，这时我们可以借助当时自动切换时刻的MHA日志来完成对原master的修复。下面是提取相关日志的命令：

  1. [root@192.168.0.20 app1]# grep -i "All other slaves should start" manager.log
  2. Mon Apr  ::  - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.0.60', MASTER_PORT=, MASTER_LOG_FILE='mysql-bin.000022', MASTER_LOG_POS=, MASTER_USER='repl', MASTER_PASSWORD='xxx';
  3. [root@192.168.0.20 app1]#

获取上述信息以后，就可以直接在修复后的master上执行change master to相关操作，重新作为从库了。

最后补充一下邮件发送脚本send_report ，这个脚本在询问一位朋友后可以使用，如下：

  1. #!/usr/bin/perl
  2.  
  3. #  Copyright (C) 2011 DeNA Co.,Ltd.
  4. #
  5. #  This program is free software; you can redistribute it and/or modify
  6. #  it under the terms of the GNU General Public License as published by
  7. #  the Free Software Foundation; either version 2 of the License, or
  8. #  (at your option) any later version.
  9. #
  10. #  This program is distributed in the hope that it will be useful,
  11. #  but WITHOUT ANY WARRANTY; without even the implied warranty of
  12. #  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  13. #  GNU General Public License for more details.
  14. #
  15. #  You should have received a copy of the GNU General Public License
  16. #   along with this program; if not, write to the Free Software
  17. #  Foundation, Inc.,
  18. #  51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
  19.  
  20. ## Note: This is a sample script and is not complete. Modify the script based on your environment.
  21.  
  22. use strict;
  23. use warnings FATAL => 'all';
  24. use Mail::Sender;
  25. use Getopt::Long;
  26.  
  27. #new_master_host and new_slave_hosts are set only when recovering master succeeded
  28. my ( $dead_master_host, $new_master_host, $new_slave_hosts, $subject, $body );
  29. my $smtp='smtp.163.com';
  30. my $mail_from='xxxx';
  31. my $mail_user='xxxxx';
  32. my $mail_pass='xxxxx';
  33. my $mail_to=['xxxx','xxxx'];
  34. GetOptions(
  35.   'orig_master_host=s' => \$dead_master_host,
  36.   'new_master_host=s'  => \$new_master_host,
  37.   'new_slave_hosts=s'  => \$new_slave_hosts,
  38.   'subject=s'          => \$subject,
  39.   'body=s'             => \$body,
  40. );
  41.  
  42. mailToContacts($smtp,$mail_from,$mail_user,$mail_pass,$mail_to,$subject,$body);
  43.  
  44. sub mailToContacts {
  45.     my ( $smtp, $mail_from, $user, $passwd, $mail_to, $subject, $msg ) = @_;
  46.     open my $DEBUG, "> /tmp/monitormail.log"
  47.         or die "Can't open the debug      file:$!\n";
  48.     my $sender = new Mail::Sender {
  49.         ctype       => 'text/plain; charset=utf-8',
  50.         encoding    => 'utf-8',
  51.         smtp        => $smtp,
  52.         from        => $mail_from,
  53.         auth        => 'LOGIN',
  54.         TLS_allowed => '0',
  55.         authid      => $user,
  56.         authpwd     => $passwd,
  57.         to          => $mail_to,
  58.         subject     => $subject,
  59.         debug       => $DEBUG
  60.     };
  61.  
  62.     $sender->MailMsg(
  63.         {   msg   => $msg,
  64.             debug => $DEBUG
  65.         }
  66.     ) or print $Mail::Sender::Error;
  67.     return ;
  68. }
  69.  
  70. # Do whatever you want here
  71.  
  72. exit ;

最后切换以后发送告警的邮件示例，注意，这个是我后续的测试，和上面环境出现的ip不一致不要在意。

总结：

目前高可用方案可以一定程度上实现数据库的高可用，比如前面文章介绍的MMM，heartbeat+drbd，Cluster等。还有percona的Galera Cluster等。这些高可用软件各有优劣。在进行高可用方案选择时，主要是看业务还有对数据一致性方面的要求。最后出于对数据库的高可用和数据一致性的要求，推荐使用MHA架构。

参考资料：

http://huoding.com/2011/12/18/139

http://blog.itpub.net/88305/viewspace-730135/

https://code.google.com/p/mysql-master-ha/wiki/TableOfContents?tm=6（自备梯子）

http://k-1-ne-jp.blogspot.com/2013/02/masterhamasterswitch_13.html（自备梯子）

MySQL高可用架构之MHA的更多相关文章

  1. mysql高可用架构之MHA，haproxy实现读写分离详解

    MySQL高可用架构之MHA 一.运维人员需要掌握的MySQL技术: 1.基本SQL语句 2.基本的管理[库表数据的管理    权限的管理] 3.容灾       保证数据不丢失. 二.工作中MySQ ...

  2. (转)MySQL高可用架构之MHA

    MySQL高可用架构之MHA  原文:http://www.cnblogs.com/gomysql/p/3675429.html 简介: MHA(Master High Availability)目前 ...

  3. 转一下大师兄的"MySQL高可用架构之MHA"

    简介: MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司youshimaton(现就职于Facebook公司)开发,是 ...

  4. MySQL高可用架构之MHA（转）

    简介: MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司youshimaton(现就职于Facebook公司)开发,是 ...

  5. mysql高可用架构之-MHA学习

    此博文参考  博主:mysql高级DBA yayun  完成 简介: MHA(Master High Availability)目前在MySQL高可用方面是一个相对成熟的解决方案,它由日本DeNA公司 ...

  6. MySQL 高可用架构 之 MHA (Centos 7.5 MySQL 5.7.18 MHA 0.58)

    目录 简介 环境准备 秘钥互信 安装基础依赖包 安装MHA组件 安装 MHA Node组件 安装 MHA Manager 组件 建立 MySQL 一主三从 初始化 MySQL 启动MySQL 并简单配 ...

  7. MySQL高可用架构之MHA 原理与实践

    MHA简介 关于MHA MHA(Master HA)是一款开源的MySQL的高可用程序,它为MySQL主从复制架构提供了automating master failover 功能.MHA在监控到mas ...

  8. 【MySQL】MySQL高可用架构之MHA

    一.关于MHA MHA(Master HA)是一款开源的MySQL的高可用程序,它为MySQL主从复制架构提供了automating master failover 功能.MHA在监控到master节 ...

  9. MySQL高可用系列之MHA（二）

    一.參数说明 MHA提供了一系列配置參数.深入理解每一个參数的详细含义,对优化配置.合理使用MHA非常重要.非常多高可用性也都是通过合理配置一些參数而实现的. MHA包含例如以下配置參数,分别说明例如 ...

随机推荐

  1. 《图解Spark：核心技术与案例实战》介绍及书附资源

    本书中所使用到的测试数据.代码和安装包放在百度盘提供 下载 ,地址为https://pan.baidu.com/s/1o8ydtKA 密码:imaa 另外在百度盘提供本书附录  下载 ,地址为http ...

  2. virtual 修饰符与继承对析构函数的影响（C++）

    以前,知道了虚函数表的低效性之后,一直尽量避免使用之.所以,在最近的工程中,所有的析构函数都不是虚函数.今天趁着还书的机会到图书馆,还书之后在 TP 分类下闲逛,偶然读到一本游戏编程书,里面说建议将存 ...

  3. CentOS下VMware用桥接模式，静态ip上外网

    15年的时候,写过一篇博客:VMware中网络设置之Bridged  也是关于linux下vmware桥接模式.静态ip上外网的配置,不过当时更多的是用图形界面来实现的,通用性不强.生产环境,极少有l ...

  4. 重温Bootstrap

    预热 ★ 学习要点 1. 理解其GridSystem(栅格排版): 2. 熟悉其所提供的各种CSS样式及显示效果: 3. 知道提供了哪些直接可用的UI组件,以及如何使用JavaScript去调整其交互 ...

  5. Hibernate-chapter one

    ======什么是Hibernate???====== Hibernate是一个开放源代码的对象关系映射框架,它对JDBC进行了非常轻量级的对象封装,它将POJO与数据库表建立映射关系,是一个全自动的 ...

  6. 关于An association from the table refers to an unmapped class

    今天配置SSH框架的时候出现这个异常,找了很久,才发现原来是是实体类映射文件中的<class name="Role" table="role">的n ...

  7. adb查询log命令

    http://blog.csdn.net/fulinwsuafcie/article/details/8028572

  8. iscroll总结

    iScroll基本信息 官网:http://cubiq.org/iscroll-4 更新:2012.07.14 版本:v4.2.5 兼容:iPhone/Ipod touch >=3.1.1, i ...

  9. jquery.dataTable.js 基础配置

    $(document).ready(function () { $('#dataTables-example').DataTable({ responsive: true, "bPagina ...

  10. js严格模式总结

    首先,我们要理解严格模式的概念,严格模式是一种特殊的执行模式,它修复了部分语言上的不足,提供更强的错误检查,病增强安全性.可以对部分函数进行执行严格模式,如: function func(){ 'us ...