接上篇文章，介绍了如何安装mysql mha，地址如下：http://blog.csdn.net/yiyuf/article/details/40340895

下面接着进行mha的相关测试：

SSH 信任关系检测：

[root@mha scripts]# masterha_check_ssh --conf=/etc/app1.cnf

Fri Oct 17 09:45:45 2014 - [info] Reading default configuration from /etc/masterha_default.cnf..

Fri Oct 17 09:45:45 2014 - [info] Reading application default configuration from /etc/app1.cnf..

Fri Oct 17 09:45:45 2014 - [info] Reading server configuration from /etc/app1.cnf..

Fri Oct 17 09:45:45 2014 - [info] Starting SSH connection tests..

Fri Oct 17 09:45:46 2014 - [debug]

Fri Oct 17 09:45:45 2014 - [debug]  Connecting via SSH from root@192.168.56.110(192.168.56.110:22) to root@192.168.56.113(192.168.56.113:22)..

Fri Oct 17 09:45:46 2014 - [debug]   ok.

Fri Oct 17 09:45:47 2014 - [debug]

Fri Oct 17 09:45:46 2014 - [debug]  Connecting via SSH from root@192.168.56.113(192.168.56.113:22) to root@192.168.56.110(192.168.56.110:22)..

Fri Oct 17 09:45:47 2014 - [debug]   ok.

Fri Oct 17 09:45:47 2014 - [info] All SSH connection tests passed successfully

[root@mha ~]# masterha_check_repl --conf=/etc/app1.cnf 
Tue Oct 21 11:06:59 2014 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Oct 21 11:06:59 2014 - [info] Reading application default configuration from /etc/app1.cnf..
Tue Oct 21 11:06:59 2014 - [info] Reading server configuration from /etc/app1.cnf..
Tue Oct 21 11:06:59 2014 - [info] MHA::MasterMonitor version 0.56.
Tue Oct 21 11:07:00 2014 - [info] GTID failover mode = 0
Tue Oct 21 11:07:00 2014 - [info] Dead Servers:
Tue Oct 21 11:07:00 2014 - [info] Alive Servers:
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.112(192.168.56.112:3306)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.113(192.168.56.113:3306)
Tue Oct 21 11:07:00 2014 - [info] Alive Slaves:
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.112(192.168.56.112:3306)  Version=5.5.40-36.1-log (oldest major version between slaves) log-bin:enabled
Tue Oct 21 11:07:00 2014 - [info]     Replicating from 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Oct 21 11:07:00 2014 - [info]   192.168.56.113(192.168.56.113:3306)  Version=5.6.21-69.0-log log-bin:enabled
Tue Oct 21 11:07:00 2014 - [info]     Replicating from 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info]     Not candidate for the new Master (no_master is set)
Tue Oct 21 11:07:00 2014 - [info] Current Alive Master: 192.168.56.110(192.168.56.110:3306)
Tue Oct 21 11:07:00 2014 - [info] Checking slave configurations..
Tue Oct 21 11:07:00 2014 - [warning]  relay_log_purge=0 is not set on slave 192.168.56.112(192.168.56.112:3306).
Tue Oct 21 11:07:00 2014 - [info] Checking replication filtering settings..
Tue Oct 21 11:07:00 2014 - [info]  binlog_do_db= , binlog_ignore_db= 
Tue Oct 21 11:07:00 2014 - [info]  Replication filtering check ok.
Tue Oct 21 11:07:00 2014 - [info] GTID (with auto-pos) is not supported
Tue Oct 21 11:07:00 2014 - [info] Starting SSH connection tests..
Tue Oct 21 11:07:06 2014 - [info] All SSH connection tests passed successfully.
Tue Oct 21 11:07:06 2014 - [info] Checking MHA Node version..
Tue Oct 21 11:07:07 2014 - [info]  Version check ok.
Tue Oct 21 11:07:07 2014 - [info] Checking SSH publickey authentication settings on the current master..
Tue Oct 21 11:07:07 2014 - [info] HealthCheck: SSH to 192.168.56.110 is reachable.
Tue Oct 21 11:07:07 2014 - [info] Master MHA Node version is 0.56.
Tue Oct 21 11:07:07 2014 - [info] Checking recovery script configurations on 192.168.56.110(192.168.56.110:3306)..
Tue Oct 21 11:07:07 2014 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/var/log/masterha/app1/save_binary_logs_test --manager_version=0.56 --start_file=561103306-bin.000010 
Tue Oct 21 11:07:07 2014 - [info]   Connecting to root@192.168.56.110(192.168.56.110:22).. 
  Creating /var/log/masterha/app1 if not exists..    ok.
  Checking output directory is accessible or not..
   ok.
  Binlog found at /var/lib/mysql, up to 561103306-bin.000010
Tue Oct 21 11:07:08 2014 - [info] Binlog setting check done.
Tue Oct 21 11:07:08 2014 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
Tue Oct 21 11:07:08 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='yyf' --slave_host=192.168.56.112 --slave_ip=192.168.56.112 --slave_port=3306 --workdir=/var/log/masterha/app1 --target_version=5.5.40-36.1-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx
Tue Oct 21 11:07:08 2014 - [info]   Connecting to root@192.168.56.112(192.168.56.112:22).. 
  Checking slave recovery environment settings..
    Opening /var/lib/mysql/relay-log.info ... ok.
    Relay log found at /var/lib/mysql, up to mysqld-relay-bin.000002
    Temporary relay log file is /var/lib/mysql/mysqld-relay-bin.000002
    Testing mysql connection and privileges.. done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Tue Oct 21 11:07:08 2014 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='yyf' --slave_host=192.168.56.113 --slave_ip=192.168.56.113 --slave_port=3306 --workdir=/var/log/masterha/app1 --target_version=5.6.21-69.0-log --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info  --relay_dir=/var/lib/mysql/  --slave_pass=xxx
Tue Oct 21 11:07:08 2014 - [info]   Connecting to root@192.168.56.113(192.168.56.113:22).. 
  Checking slave recovery environment settings..
    Opening /var/lib/mysql/relay-log.info ... ok.
    Relay log found at /var/lib/mysql, up to mysqld-relay-bin.000002
    Temporary relay log file is /var/lib/mysql/mysqld-relay-bin.000002
    Testing mysql connection and privileges..Warning: Using a password on the command line interface can be insecure.
 done.
    Testing mysqlbinlog output.. done.
    Cleaning up test file(s).. done.
Tue Oct 21 11:07:17 2014 - [info] Slaves settings check done.
Tue Oct 21 11:07:17 2014 - [info] 
192.168.56.110(192.168.56.110:3306) (current master)
 +--192.168.56.112(192.168.56.112:3306)
 +--192.168.56.113(192.168.56.113:3306)
Tue Oct 21 11:07:17 2014 - [info] Checking replication health on 192.168.56.112..
Tue Oct 21 11:07:17 2014 - [info]  ok.
Tue Oct 21 11:07:17 2014 - [info] Checking replication health on 192.168.56.113..
Tue Oct 21 11:07:17 2014 - [info]  ok.
Tue Oct 21 11:07:17 2014 - [info] Checking master_ip_failover_script status:
Tue Oct 21 11:07:17 2014 - [info]   /root/scripts/master_ip_failover.sh --command=status --ssh_user=root --orig_master_host=192.168.56.110 --orig_master_ip=192.168.56.110 --orig_master_port=3306 
IN SCRIPT TEST====/etc/init.d/keepalived stop==/etc/init.d/keepalived start===
Checking the Status of the script.. OK 
Tue Oct 21 11:07:17 2014 - [info]  OK.
Tue Oct 21 11:07:17 2014 - [warning] shutdown_script is not defined.
Tue Oct 21 11:07:17 2014 - [info] Got exit code 0 (Not master dead).
MySQL Replication Health is OK.

MySQL MHA相关测试的更多相关文章

  1. MySQL MHA+Keepalived

    一.MHA的简单介绍MHA是由perl语言编写的,用外挂脚本的方式实现mysql主从复制的高可用性.MHA可以自动检测mysql是否宕机,如果宕机,在10-30s内完成new master的选举,应用 ...

  2. MYSQL MHA

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

  3. 搭建MySQL MHA高可用

    本文内容参考:http://www.ttlsa.com/mysql/step-one-by-one-deploy-mysql-mha-cluster/ MySQL MHA 高可用集群 环境: Linu ...

  4. CENTOS6.6 下mysql MHA架构搭建

    本文来自我的github pages博客http://galengao.github.io/ 即www.gaohuirong.cn 摘要: 本篇是自己搭建的一篇mysql MHA文章 前面的安装步骤基 ...

  5. mysql MHA架构搭建过程

    [环境介绍] 系统环境:Red Hat Enterprise Linux 7 + 5.7.18 + MHA version 0.57 系统 IP 主机名 备注 版本 xx系统 192.168.142. ...

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

    转载请注明出处,本文地址:http://www.cnblogs.com/ajiangg/p/6552855.html 以下是CentOS6.8下MySQL MHA架构搭建笔记 IP资源规划: 192. ...

  7. MySQL MHA 搭建&测试（环境：CentOS7 + MySQL5.7.23）

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

  8. 基于Docker Compose构建的MySQL MHA集群

    Docker MySQL MHA 基于Docker 1.13.1之上构建的MySQL MHA Docker Compose Project 可快速启动GTID模式下的MasterHA集群, 主用于My ...

  9. 基于MySQL+MHA+Haproxy部署高可用负载均衡集群

    一.MHA 概述 MHA(Master High Availability)是可以在MySQL上使用的一套高可用方案.所编写的语言为Perl 从名字上我们可以看到.MHA的目的就是为了维护Master ...

随机推荐

  1. Codeforces 850A - Five Dimensional Points(暴力)

    原题链接:http://codeforces.com/problemset/problem/850/A 题意:有n个五维空间内的点,如果其中三个点A,B,C,向量AB,AC的夹角不大于90°,则点A是 ...

  2. MySQL server has gone away 问题解决方法

    问题描述: SQLyog在执行大的sql文件时候,报错,报错日志显示2006 - MySQL server has gone away 解决办法: 在php.ini配置文件的[mysqld]节点下添加 ...

  3. （转）pd.read_csv之OSError: Initializing from file failed的解决方案

    转:https://blog.csdn.net/funnyPython/article/details/78532102 rides = pd.read_csv(data_path)1 # OSErr ...

  4. DHCP服务器怎么设置怎么启动

    DHCP:动态主机配置协议,服务器用于为网络中的客户端自动分配IP地址.这种方法避免了由于手动配置IP地址导致的IP地址冲突问题,同时也减少了网络管理员的工作量. 工具/原料 在配置DHCP服务器时, ...

  5. Gym 100917F Find the Length

    题目链接:http://codeforces.com/gym/100917/problem/F ---------------------------------------------------- ...

  6. C#-概念-接口：接口

    ylbtech-C#-概念-接口:接口 接口(硬件类接口)是指同一计算机不同功能层之间的通信规则称为接口. 接口(软件类接口)是指对协定进行定义的引用类型.其他类型实现接口,以保证它们支持某些操作.接 ...

  7. 128、TensorFlow元数据MetaData

    #tf.Session.run也接收一个可选的参数options #能够让你来配置训练时的参数 #run_metadata参数让你能够收集关于训练的元信息 #列如你可以使用这些可选项来追踪执行的信息 ...

  8. Oracle-创建索引分区

    对大数据量索引进行分区同样能够优化应用系统的性能.一般来说,如果索引所对应的表的数据量非常大,比如几百万甚至上千万条数据,则索引也会占用很大的空间,这时,建议对索引进行分区. Oracle索引分区分为 ...

  9. HBase备份还原OpenTSDB数据之Snapshot

    前言 本文基于伪分布式搭建 hadoop+zookeeper+hbase+opentsdb之后,想了解前因后果的可以看上一篇和上上篇. opentsdb在hbase中生成4个表(tsdb, tsdb- ...

  10. vue+element-ui国际化（i18n）

    1. 下载element-ui和vue-i18n: npm i element-ui --save   npm i vue-i18n –save 2.  创建一个  i18n 文件夹, 在main.j ...