191145686 发表于 2018-9-27 10:16:22

实现MySQL,MHA高可用集群架构

# masterha_check_repl --conf=/etc/mha/app1.cnf  Sat Mar 31 19:19:26 2018 - Global configuration file /etc/masterha_default.cnf not found. Skipping.
  Sat Mar 31 19:19:26 2018 - Reading application default configuration from /etc/mha/app1.cnf..
  Sat Mar 31 19:19:26 2018 - Reading server configuration from /etc/mha/app1.cnf..
  Sat Mar 31 19:19:26 2018 - MHA::MasterMonitor version 0.56.
  Sat Mar 31 19:19:28 2018 - GTID failover mode = 0
  Sat Mar 31 19:19:28 2018 - Dead Servers:
  Sat Mar 31 19:19:28 2018 - Alive Servers:
  Sat Mar 31 19:19:28 2018 -    172.18.30.107(172.18.30.107:3306)
  Sat Mar 31 19:19:28 2018 -    172.18.30.108(172.18.30.108:3306)
  Sat Mar 31 19:19:28 2018 -    172.18.30.109(172.18.30.109:3306)
  Sat Mar 31 19:19:28 2018 - Alive Slaves:
  Sat Mar 31 19:19:28 2018 -    172.18.30.108(172.18.30.108:3306)Version=5.5.56-MariaDB (oldest major version between slaves) log-bin:enabled
  Sat Mar 31 19:19:28 2018 -    Replicating from 172.18.30.107(172.18.30.107:3306)
  Sat Mar 31 19:19:28 2018 -    Primary candidate for the new Master (candidate_master is set)
  Sat Mar 31 19:19:28 2018 -    172.18.30.109(172.18.30.109:3306)Version=5.5.56-MariaDB (oldest major version between slaves) log-bin:enabled
  Sat Mar 31 19:19:28 2018 -    Replicating from 172.18.30.107(172.18.30.107:3306)
  Sat Mar 31 19:19:28 2018 -    Primary candidate for the new Master (candidate_master is set)
  Sat Mar 31 19:19:28 2018 - Current Alive Master: 172.18.30.107(172.18.30.107:3306)
  Sat Mar 31 19:19:28 2018 - Checking slave configurations..
  Sat Mar 31 19:19:28 2018 - read_only=1 is not set on slave 172.18.30.108(172.18.30.108:3306).

  Sat Mar 31 19:19:28 2018 - >  Sat Mar 31 19:19:28 2018 - read_only=1 is not set on slave 172.18.30.109(172.18.30.109:3306).

  Sat Mar 31 19:19:28 2018 - >  Sat Mar 31 19:19:28 2018 - Checking replication filtering settings..
  Sat Mar 31 19:19:28 2018 - binlog_do_db= , binlog_ignore_db=
  Sat Mar 31 19:19:28 2018 - Replication filtering check ok.
  Sat Mar 31 19:19:28 2018 - GTID (with auto-pos) is not supported
  Sat Mar 31 19:19:28 2018 - Starting SSH connection tests..
  Sat Mar 31 19:19:31 2018 - All SSH connection tests passed successfully.
  Sat Mar 31 19:19:31 2018 - Checking MHA Node version..
  Sat Mar 31 19:19:32 2018 - Version check ok.
  Sat Mar 31 19:19:32 2018 - Checking SSH publickey authentication settings on the current master..
  Sat Mar 31 19:19:33 2018 - HealthCheck: SSH to 172.18.30.107 is reachable.
  Sat Mar 31 19:19:34 2018 - Master MHA Node version is 0.56.
  Sat Mar 31 19:19:34 2018 - Checking recovery script configurations on 172.18.30.107(172.18.30.107:3306)..
  Sat Mar 31 19:19:34 2018 -    Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/var/lib/mysql,/var/log/mysql --output_file=/data/mastermha/app1//save_binary_logs_test --manager_version=0.56 --start_file=mariadb-bin.000001
  Sat Mar 31 19:19:34 2018 -    Connecting to root@172.18.30.107(172.18.30.107:22)..
  Creating /data/mastermha/app1 if not exists..    ok.
  Checking output directory is accessible or not..
  ok.
  Binlog found at /var/lib/mysql, up to mariadb-bin.000001
  Sat Mar 31 19:19:34 2018 - Binlog setting check done.
  Sat Mar 31 19:19:34 2018 - Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
  Sat Mar 31 19:19:34 2018 -    Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=172.18.30.108 --slave_ip=172.18.30.108 --slave_port=3306 --workdir=/data/mastermha/app1/ --target_version=5.5.56-MariaDB --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info--relay_dir=/var/lib/mysql/--slave_pass=xxx
  Sat Mar 31 19:19:34 2018 -    Connecting to root@172.18.30.108(172.18.30.108:22)..
  Checking slave recovery environment settings..
  Opening /var/lib/mysql/relay-log.info ... ok.
  Relay log found at /var/lib/mysql, up to mariadb-relay-bin.000002

  Temporary>  Testing mysql connection and privileges.. done.
  Testing mysqlbinlog output.. done.
  Cleaning up test file(s).. done.
  Sat Mar 31 19:19:35 2018 -    Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=172.18.30.109 --slave_ip=172.18.30.109 --slave_port=3306 --workdir=/data/mastermha/app1/ --target_version=5.5.56-MariaDB --manager_version=0.56 --relay_log_info=/var/lib/mysql/relay-log.info--relay_dir=/var/lib/mysql/--slave_pass=xxx
  Sat Mar 31 19:19:35 2018 -    Connecting to root@172.18.30.109(172.18.30.109:22)..
  Checking slave recovery environment settings..
  Opening /var/lib/mysql/relay-log.info ... ok.
  Relay log found at /var/lib/mysql, up to mariadb-relay-bin.000002

  Temporary>  Testing mysql connection and privileges.. done.
  Testing mysqlbinlog output.. done.
  Cleaning up test file(s).. done.
  Sat Mar 31 19:19:36 2018 - Slaves settings check done.
  Sat Mar 31 19:19:36 2018 -
  172.18.30.107(172.18.30.107:3306) (current master)
  +--172.18.30.108(172.18.30.108:3306)
  +--172.18.30.109(172.18.30.109:3306)
  Sat Mar 31 19:19:36 2018 - Checking replication health on 172.18.30.108..
  Sat Mar 31 19:19:36 2018 - ok.
  Sat Mar 31 19:19:36 2018 - Checking replication health on 172.18.30.109..
  Sat Mar 31 19:19:36 2018 - ok.
  Sat Mar 31 19:19:36 2018 - master_ip_failover_script is not defined.
  Sat Mar 31 19:19:36 2018 - shutdown_script is not defined.
  Sat Mar 31 19:19:36 2018 - Got exit code 0 (Not master dead).
  MySQL Replication Health is OK.

页: [1]
查看完整版本: 实现MySQL,MHA高可用集群架构