1 准备工作

1.1 修改主机名

  1. vim  /etc/hosts
  2.  
  3. # 添加对应主机
  4.  
  5. 192.168.28.128 mha1
  6. 192.168.28.131 mha2
  7. 192.168.28.132 mha3

1.2 关闭防火墙及修改selinux

  1. # 关闭防火墙
  2. systemctl  stop firewalld
    systemctl  disable firewalld   # 关闭自启动
  3.  
  4. # 修改selinux
  5. vim  /etc/sysconfig/selinux
  6. SELINUX=disabled  #  设置为disabled

1.3 部署一套1主2从的MySQL集群

创建主从可以参考MySQL主从搭建

注意必须有如下参数

  1. server-id=                    #  每个节点不能相同
  2. log-bin=/data/mysql3306/logs/mysql-bin
  3. relay-log=/data/mysql3306/logs/relay-log
  4. skip-name-resolve              #  建议加上 非必须项
  5. #read_only = ON                #  从库开启，主库关闭只读
  6. relay_log_purge =             #  关闭自动清理中继日志
  7. log_slave_updates =           #  从库通过binlog更新的数据写进从库二进制日志中，必加，否则切换后可能丢失数据
  8.

创建mha管理账号

  1. # 特别注意： mha的密码不要出现特殊字符，否则后面无法切换主库
    create user  mha@'192.168.28.%' identified by 'MHAadmin123';
  2.  
  3. create user  mha@'localhost' identified by 'MHAadmin123';
  4.  
  5. grant all on *.* to   mha@'192.168.28.%';
  6. grant all on *.* to   mha@'localhost';

1.4  配置互信

MHA管理节点上执行（但建议每台主机均执行，便于切换管理节点及集群间维护，但注意主机安全），包含本机到本机的互信

  1. ssh-keygen
  2. ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.28.128
  3. ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.28.131
  4. ssh-copy-id -i ~/.ssh/id_rsa.pub root@192.168.28.132

配置完成后记得测试一下是否配置成功（必须测试）

  1.  ssh root@192.168.28.128
  2.  ssh root@192.168.28.131
  3.  ssh root@192.168.28.132
  4.  ssh root@mha1
  5.  ssh root@mha2
  6.  ssh root@mha3

2  MHA工具部署

2.1 安装MHA相关依赖包

  1.   yum install perl-DBI perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Time-HiRes perl-Params-Validate perl-DateTime -y
  2.   yum install perl-ExtUtils-Embed -y
  3.   yum install cpan -y
  4.   yum install perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker -y

注意： MySQL数据库安装时不建议用rpm包方式安装，否则此处部分包可能有冲突

2.2 安装MHA 管理及node节点

  1. # 所有节点均需安装
  2.  rpm -ivh  mha4mysql-node-0.58-.el7.centos.noarch.rpm
  3.  
  4. #管理节点需安装（其他节点也可以安装）
  5. mha4mysql-manager-0.58-.el7.centos.noarch.rpm

如果以上安装包未安装全，则会出现类似下面的错误，如出现可以调整yum源或找下载好的同学获取

  1. [root@mha3 local]# rpm -ivh  mha4mysql-manager-0.58-.el7.centos.noarch.rpm
  2. error: Failed dependencies:
  3.     perl(Log::Dispatch) is needed by mha4mysql-manager-0.58-.el7.centos.noarch
  4.     perl(Log::Dispatch::File) is needed by mha4mysql-manager-0.58-.el7.centos.noarch
  5.     perl(Log::Dispatch::Screen) is needed by mha4mysql-manager-0.58-.el7.centos.noarch
  6.     perl(Parallel::ForkManager) is needed by mha4mysql-manager-0.58-.el7.centos.noarch

2.3 配置mha

创建配置文件路径、日志文件路径

  1. mkdir -p /etc/masterha
  2. mkdir -p /var/log/masterha/app1

创建mha配置文件

  1. vim  /etc/masterha/app1.conf
  2.  
  3. user=mha
  4. [server default]
  5. manager_workdir=/var/log/masterha/app1
  6. manager_log=/var/log/masterha/app1/app1.log
  7. master_ip_failover_script=/usr/bin/master_ip_failover
  8. master_ip_online_change_script=/usr/bin/master_ip_online_change
  9.  
  10. ##mysql用户名和密码
  11. user=mha
  12. password=MHAadmin123
  13. ssh_user=root
  14. repl_user=repl
  15. repl_password=repl
  16. ping_interval=3
  17. remote_workdir=/tmp
  18. report_script=/usr/bin/send_report
    # secondary_check_script 可以不加
  19. # secondary_check_script=/usr/bin/masterha_secondary_check -s mha2 -s mha3 --user=mha --master_host=mha1 --master_ip=192.168.28.128 --master_port=3306 --password=MHAadmin123
  20. shutdown_script=""
  21. report_script=""
  22.  
  23. [server1]
  24. hostname=192.168.28.128
  25. master_binlog_dir=/data/mysql3306/logs
  26. candidate_master=1
  27.  
  28. [server2]
  29. hostname=192.168.28.131
  30. master_binlog_dir=/data/mysql3306/logs
  31. candidate_master=1
  32. check_repl_delay=0
  33.  
  34. [server3]
  35. hostname=192.168.28.132
  36. master_binlog_dir=/data/mysql3306/logs
  37. no_master=1

配置两个重要的脚本  master_ip_failover 、 master_ip_online_change

/usr/bin/master_ip_failover

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

/usr/bin/master_ip_online_change

  1. vim /usr/bin/master_ip_online_change
  2. #!/usr/bin/env perl
  3.  
  4. use strict;
  5. use warnings FATAL => 'all';
  6.  
  7. use Getopt::Long;
  8.  
  9. #my (
  10. #    $command,          $ssh_user,        $orig_master_host, $orig_master_ip,
  11. #    $orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
  12. #);
  13.  
  14. my (
  15.   $command,              $orig_master_is_new_slave, $orig_master_host,
  16.   $orig_master_ip,       $orig_master_port,         $orig_master_user,
  17.   $orig_master_password, $orig_master_ssh_user,     $new_master_host,
  18.   $new_master_ip,        $new_master_port,          $new_master_user,
  19.   $new_master_password,  $new_master_ssh_user,
  20. );
  21.  
  22. my $vip = '192.168.28.199/24';
  23. my $if = 'ens33';
  24. my $ssh_start_vip = "/sbin/ip addr add $vip dev $if";
  25. my $ssh_stop_vip = "/sbin/ip addr del $vip dev $if";
  26. my $ssh_user = "root";
  27.  
  28. GetOptions(
  29.     'command=s'          => \$command,
  30.     #'ssh_user=s'         => \$ssh_user,
  31.     #'orig_master_host=s' => \$orig_master_host,
  32.     #'orig_master_ip=s'   => \$orig_master_ip,
  33.     #'orig_master_port=i' => \$orig_master_port,
  34.     #'new_master_host=s'  => \$new_master_host,
  35.     #'new_master_ip=s'    => \$new_master_ip,
  36.     #'new_master_port=i'  => \$new_master_port,
  37.     'orig_master_is_new_slave' => \$orig_master_is_new_slave,
  38.     'orig_master_host=s'       => \$orig_master_host,
  39.     'orig_master_ip=s'         => \$orig_master_ip,
  40.     'orig_master_port=i'       => \$orig_master_port,
  41.     'orig_master_user=s'       => \$orig_master_user,
  42.     'orig_master_password=s'   => \$orig_master_password,
  43.     'orig_master_ssh_user=s'   => \$orig_master_ssh_user,
  44.     'new_master_host=s'        => \$new_master_host,
  45.     'new_master_ip=s'          => \$new_master_ip,
  46.     'new_master_port=i'        => \$new_master_port,
  47.     'new_master_user=s'        => \$new_master_user,
  48.     'new_master_password=s'    => \$new_master_password,
  49.     'new_master_ssh_user=s'    => \$new_master_ssh_user,
  50. );
  51.  
  52. exit &main();
  53.  
  54. sub main {
  55.  
  56.     print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";
  57.  
  58.     if ( $command eq "stop" || $command eq "stopssh" ) {
  59.  
  60.         my $exit_code = 1;
  61.         eval {
  62.             print "Disabling the VIP on old master: $orig_master_host \n";
  63.             &stop_vip();
  64.             $exit_code = 0;
  65.         };
  66.         if ($@) {
  67.             warn "Got Error: $@\n";
  68.             exit $exit_code;
  69.         }
  70.         exit $exit_code;
  71.     }
  72.     elsif ( $command eq "start" ) {
  73.  
  74.         my $exit_code = 10;
  75.         eval {
  76.             print "Enabling the VIP - $vip on the new master - $new_master_host \n";
  77.             &start_vip();
  78.             $exit_code = 0;
  79.         };
  80.         if ($@) {
  81.             warn $@;
  82.             exit $exit_code;
  83.         }
  84.         exit $exit_code;
  85.     }
  86.     elsif ( $command eq "status" ) {
  87.         print "Checking the Status of the script.. OK \n";
  88.         exit 0;
  89.     }
  90.     else {
  91.         &usage();
  92.         exit 1;
  93.     }
  94. }
  95.  
  96. sub start_vip() {
  97.     `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
  98. }
  99. sub stop_vip() {
  100.      return 0  unless  ($ssh_user);
  101.     `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
  102. }
  103.  
  104. sub usage {
  105.     print
  106.     "Usage: master_ip_failover --command=start|stop|stopssh|status --ssh-user=user --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";
  107. }

2.4  相关检测

检测互信

检查各节点互信是否正常，类似于之前的检查，此处有脚本实现检查

  1. [root@mha3 app1]# masterha_check_ssh --conf=/etc/masterha/app1.conf
  2. Sun May 24 17:33:08 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  3. Sun May 24 17:33:08 2020 - [info] Reading application default configuration from /etc/masterha/app1.conf..
  4. Sun May 24 17:33:08 2020 - [info] Reading server configuration from /etc/masterha/app1.conf..
  5. Sun May 24 17:33:08 2020 - [info] Starting SSH connection tests..
  6. Sun May 24 17:33:12 2020 - [debug]
  7. Sun May 24 17:33:08 2020 - [debug]  Connecting via SSH from root@192.168.28.131(192.168.28.131:22) to root@192.168.28.128(192.168.28.128:22)..
  8. Sun May 24 17:33:10 2020 - [debug]   ok.
  9. Sun May 24 17:33:10 2020 - [debug]  Connecting via SSH from root@192.168.28.131(192.168.28.131:22) to root@192.168.28.132(192.168.28.132:22)..
  10. Sun May 24 17:33:12 2020 - [debug]   ok.
  11. Sun May 24 17:33:12 2020 - [debug]
  12. Sun May 24 17:33:08 2020 - [debug]  Connecting via SSH from root@192.168.28.128(192.168.28.128:22) to root@192.168.28.131(192.168.28.131:22)..
  13. Sun May 24 17:33:09 2020 - [debug]   ok.
  14. Sun May 24 17:33:09 2020 - [debug]  Connecting via SSH from root@192.168.28.128(192.168.28.128:22) to root@192.168.28.132(192.168.28.132:22)..
  15. Sun May 24 17:33:12 2020 - [debug]   ok.
  16. Sun May 24 17:33:13 2020 - [debug]
  17. Sun May 24 17:33:09 2020 - [debug]  Connecting via SSH from root@192.168.28.132(192.168.28.132:22) to root@192.168.28.128(192.168.28.128:22)..
  18. Sun May 24 17:33:11 2020 - [debug]   ok.
  19. Sun May 24 17:33:11 2020 - [debug]  Connecting via SSH from root@192.168.28.132(192.168.28.132:22) to root@192.168.28.131(192.168.28.131:22)..
  20. Sun May 24 17:33:13 2020 - [debug]   ok.
  21. Sun May 24 17:33:13 2020 - [info] All SSH connection tests passed successfully.

检查复制集群是否正常

如按照我之前的步骤配置，则此处会有如下异常

  1. masterha_check_repl --conf=/etc/masterha/app1.conf
  2.  
  3. Sun May 24 17:34:02 2020 - [info] Connecting to root@192.168.28.131(192.168.28.131:22)..
  4. Can't exec "mysqlbinlog": No such file or directory at /usr/share/perl5/vendor_perl/MHA/BinlogManager.pm line 106.
  5. mysqlbinlog version command failed with rc 1:0, please verify PATH, LD_LIBRARY_PATH, and client options
  6. at /usr/bin/apply_diff_relay_logs line 532.

报错信息很明确，找不到mysqlbinlog命令,处理方式比较简单，做个软连接即可

  1.  ln -s /usr/local/mysql5.7/bin/mysql /usr/bin/
  2.  ln -s /usr/local/mysql5.7/bin/mysqlbinlog /usr/bin/

再进行检测

  1. [root@mha3 app1]# masterha_check_repl --conf=/etc/masterha/app1.conf
  2. Sun May 24 17:34:41 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  3. Sun May 24 17:34:41 2020 - [info] Reading application default configuration from /etc/masterha/app1.conf..
  4. Sun May 24 17:34:41 2020 - [info] Reading server configuration from /etc/masterha/app1.conf..
  5. Sun May 24 17:34:41 2020 - [info] MHA::MasterMonitor version 0.58.
  6. Sun May 24 17:34:42 2020 - [info] GTID failover mode = 0
  7. Sun May 24 17:34:42 2020 - [info] Dead Servers:
  8. Sun May 24 17:34:42 2020 - [info] Alive Servers:
  9. Sun May 24 17:34:42 2020 - [info]   192.168.28.128(192.168.28.128:3306)
  10. Sun May 24 17:34:42 2020 - [info]   192.168.28.131(192.168.28.131:3306)
  11. Sun May 24 17:34:42 2020 - [info]   192.168.28.132(192.168.28.132:3306)
  12. Sun May 24 17:34:42 2020 - [info] Alive Slaves:
  13. Sun May 24 17:34:42 2020 - [info]   192.168.28.131(192.168.28.131:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  14. Sun May 24 17:34:42 2020 - [info]     Replicating from 192.168.28.128(192.168.28.128:3306)
  15. Sun May 24 17:34:42 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
  16. Sun May 24 17:34:42 2020 - [info]   192.168.28.132(192.168.28.132:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  17. Sun May 24 17:34:42 2020 - [info]     Replicating from 192.168.28.128(192.168.28.128:3306)
  18. Sun May 24 17:34:42 2020 - [info]     Not candidate for the new Master (no_master is set)
  19. Sun May 24 17:34:42 2020 - [info] Current Alive Master: 192.168.28.128(192.168.28.128:3306)
  20. Sun May 24 17:34:42 2020 - [info] Checking slave configurations..
  21. Sun May 24 17:34:42 2020 - [info] Checking replication filtering settings..
  22. Sun May 24 17:34:42 2020 - [info]  binlog_do_db= , binlog_ignore_db=
  23. Sun May 24 17:34:42 2020 - [info]  Replication filtering check ok.
  24. Sun May 24 17:34:42 2020 - [info] GTID (with auto-pos) is not supported
  25. Sun May 24 17:34:42 2020 - [info] Starting SSH connection tests..
  26. Sun May 24 17:34:48 2020 - [info] All SSH connection tests passed successfully.
  27. Sun May 24 17:34:48 2020 - [info] Checking MHA Node version..
  28. Sun May 24 17:34:49 2020 - [info]  Version check ok.
  29. Sun May 24 17:34:49 2020 - [info] Checking SSH publickey authentication settings on the current master..
  30. Sun May 24 17:34:50 2020 - [info] HealthCheck: SSH to 192.168.28.128 is reachable.
  31. Sun May 24 17:34:51 2020 - [info] Master MHA Node version is 0.58.
  32. Sun May 24 17:34:51 2020 - [info] Checking recovery script configurations on 192.168.28.128(192.168.28.128:3306)..
  33. Sun May 24 17:34:51 2020 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data/mysql3306/data --output_file=/tmp/save_binary_logs_test --manager_version=0.58 --start_file=mysql-bin.000012
  34. Sun May 24 17:34:51 2020 - [info]   Connecting to root@192.168.28.128(192.168.28.128:22)..
  35.   Creating /tmp if not exists..    ok.
  36.   Checking output directory is accessible or not..
  37.    ok.
  38.   Binlog found at /data/mysql3306/data, up to mysql-bin.000012
  39. Sun May 24 17:34:52 2020 - [info] Binlog setting check done.
  40. Sun May 24 17:34:52 2020 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
  41. Sun May 24 17:34:52 2020 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.28.131 --slave_ip=192.168.28.131 --slave_port=3306 --workdir=/tmp --target_version=5.7.25-28-log --manager_version=0.58 --relay_log_info=/data/mysql3306/data/relay-log.info  --relay_dir=/data/mysql3306/data/  --slave_pass=xxx
  42. Sun May 24 17:34:52 2020 - [info]   Connecting to root@192.168.28.131(192.168.28.131:22)..
  43.   Checking slave recovery environment settings..
  44.     Opening /data/mysql3306/data/relay-log.info ... ok.
  45.     Relay log found at /data/mysql3306/data, up to relay-log.000003
  46.     Temporary relay log file is /data/mysql3306/data/relay-log.000003
  47.     Checking if super_read_only is defined and turned on.. not present or turned off, ignoring.
  48.     Testing mysql connection and privileges..
  49. mysql: [Warning] Using a password on the command line interface can be insecure.
  50.  done.
  51.     Testing mysqlbinlog output.. done.
  52.     Cleaning up test file(s).. done.
  53. Sun May 24 17:34:53 2020 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.28.132 --slave_ip=192.168.28.132 --slave_port=3306 --workdir=/tmp --target_version=5.7.25-28-log --manager_version=0.58 --relay_log_info=/data/mysql3306/data/relay-log.info  --relay_dir=/data/mysql3306/data/  --slave_pass=xxx
  54. Sun May 24 17:34:53 2020 - [info]   Connecting to root@192.168.28.132(192.168.28.132:22)..
  55.   Checking slave recovery environment settings..
  56.     Opening /data/mysql3306/data/relay-log.info ... ok.
  57.     Relay log found at /data/mysql3306/data, up to relay-log.000003
  58.     Temporary relay log file is /data/mysql3306/data/relay-log.000003
  59.     Checking if super_read_only is defined and turned on.. not present or turned off, ignoring.
  60.     Testing mysql connection and privileges..
  61. mysql: [Warning] Using a password on the command line interface can be insecure.
  62.  done.
  63.     Testing mysqlbinlog output.. done.
  64.     Cleaning up test file(s).. done.
  65. Sun May 24 17:34:54 2020 - [info] Slaves settings check done.
  66. Sun May 24 17:34:54 2020 - [info]
  67. 192.168.28.128(192.168.28.128:3306) (current master)
  68.  +--192.168.28.131(192.168.28.131:3306)
  69.  +--192.168.28.132(192.168.28.132:3306)
  70.  
  71. Sun May 24 17:34:54 2020 - [info] Checking replication health on 192.168.28.131..
  72. Sun May 24 17:34:54 2020 - [info]  ok.
  73. Sun May 24 17:34:54 2020 - [info] Checking replication health on 192.168.28.132..
  74. Sun May 24 17:34:54 2020 - [info]  ok.
  75. Sun May 24 17:34:54 2020 - [info] Checking master_ip_failover_script status:
  76. Sun May 24 17:34:54 2020 - [info]   /usr/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.28.128 --orig_master_ip=192.168.28.128 --orig_master_port=3306 
  77.  
  78. IN SCRIPT TEST====/sbin/ip addr del 192.168.28.199/24 dev ens33==/sbin/ip addr add  192.168.28.199/24 dev  ens33===
  79.  
  80. Checking the Status of the script.. OK
  81. Sun May 24 17:34:54 2020 - [info]  OK.
  82. Sun May 24 17:34:54 2020 - [warning] shutdown_script is not defined.
  83. Sun May 24 17:34:54 2020 - [info] Got exit code 0 (Not master dead).
  84.  
  85. MySQL Replication Health is OK.

看到 "MySQL Replication Health is OK." 代表检测通过。

3  MHA测试

3.1  开启MHA服务

开启MHA服务的脚本如下，也可以写成脚本或服务

  1. nohup masterha_manager --conf=/etc/masterha/app1.conf < /dev/null > /var/log/masterha/app1/manager.log 2>&1 &

开启服务后，日志如下，与集群检测类似

  1. Sun May 24 18:31:54 2020 - [info] MHA::MasterMonitor version 0.58.
  2. Sun May 24 18:31:55 2020 - [info] GTID failover mode = 0
  3. Sun May 24 18:31:55 2020 - [info] Dead Servers:
  4. Sun May 24 18:31:55 2020 - [info] Alive Servers:
  5. Sun May 24 18:31:55 2020 - [info]   192.168.28.128(192.168.28.128:3306)
  6. Sun May 24 18:31:55 2020 - [info]   192.168.28.131(192.168.28.131:3306)
  7. Sun May 24 18:31:55 2020 - [info]   192.168.28.132(192.168.28.132:3306)
  8. Sun May 24 18:31:55 2020 - [info] Alive Slaves:
  9. Sun May 24 18:31:55 2020 - [info]   192.168.28.131(192.168.28.131:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  10. Sun May 24 18:31:55 2020 - [info]     Replicating from 192.168.28.128(192.168.28.128:3306)
  11. Sun May 24 18:31:55 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
  12. Sun May 24 18:31:55 2020 - [info]   192.168.28.132(192.168.28.132:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  13. Sun May 24 18:31:55 2020 - [info]     Replicating from 192.168.28.128(192.168.28.128:3306)
  14. Sun May 24 18:31:55 2020 - [info]     Not candidate for the new Master (no_master is set)
  15. Sun May 24 18:31:55 2020 - [info] Current Alive Master: 192.168.28.128(192.168.28.128:3306)
  16. Sun May 24 18:31:55 2020 - [info] Checking slave configurations..
  17. Sun May 24 18:31:55 2020 - [info] Checking replication filtering settings..
  18. Sun May 24 18:31:55 2020 - [info]  binlog_do_db= , binlog_ignore_db=
  19. Sun May 24 18:31:55 2020 - [info]  Replication filtering check ok.
  20. Sun May 24 18:31:55 2020 - [info] GTID (with auto-pos) is not supported
  21. Sun May 24 18:31:55 2020 - [info] Starting SSH connection tests..
  22. Sun May 24 18:32:01 2020 - [info] All SSH connection tests passed successfully.
  23. Sun May 24 18:32:01 2020 - [info] Checking MHA Node version..
  24. Sun May 24 18:32:03 2020 - [info]  Version check ok.
  25. Sun May 24 18:32:03 2020 - [info] Checking SSH publickey authentication settings on the current master..
  26. Sun May 24 18:32:03 2020 - [info] HealthCheck: SSH to 192.168.28.128 is reachable.
  27. Sun May 24 18:32:04 2020 - [info] Master MHA Node version is 0.58.
  28. Sun May 24 18:32:04 2020 - [info] Checking recovery script configurations on 192.168.28.128(192.168.28.128:3306)..
  29. Sun May 24 18:32:04 2020 - [info]   Executing command: save_binary_logs --command=test --start_pos=4 --binlog_dir=/data/mysql3306/data --output_file=/tmp/save_binary_logs_test --manager_version=0.58 --start_file=mysql-bin.000013
  30. Sun May 24 18:32:04 2020 - [info]   Connecting to root@192.168.28.128(192.168.28.128:22)..
  31.   Creating /tmp if not exists..    ok.
  32.   Checking output directory is accessible or not..
  33.    ok.
  34.   Binlog found at /data/mysql3306/data, up to mysql-bin.000013
  35. Sun May 24 18:32:05 2020 - [info] Binlog setting check done.
  36. Sun May 24 18:32:05 2020 - [info] Checking SSH publickey authentication and checking recovery script configurations on all alive slave servers..
  37. Sun May 24 18:32:05 2020 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.28.131 --slave_ip=192.168.28.131 --slave_port=3306 --workdir=/tmp --target_version=5.7.25-28-log --manager_version=0.58 --relay_log_info=/data/mysql3306/data/relay-log.info  --relay_dir=/data/mysql3306/data/  --slave_pass=xxx
  38. Sun May 24 18:32:05 2020 - [info]   Connecting to root@192.168.28.131(192.168.28.131:22)..
  39.   Checking slave recovery environment settings..
  40.     Opening /data/mysql3306/data/relay-log.info ... ok.
  41.     Relay log found at /data/mysql3306/data, up to relay-log.000005
  42.     Temporary relay log file is /data/mysql3306/data/relay-log.000005
  43.     Checking if super_read_only is defined and turned on.. not present or turned off, ignoring.
  44.     Testing mysql connection and privileges..
  45. mysql: [Warning] Using a password on the command line interface can be insecure.
  46.  done.
  47.     Testing mysqlbinlog output.. done.
  48.     Cleaning up test file(s).. done.
  49. Sun May 24 18:32:06 2020 - [info]   Executing command : apply_diff_relay_logs --command=test --slave_user='mha' --slave_host=192.168.28.132 --slave_ip=192.168.28.132 --slave_port=3306 --workdir=/tmp --target_version=5.7.25-28-log --manager_version=0.58 --relay_log_info=/data/mysql3306/data/relay-log.info  --relay_dir=/data/mysql3306/data/  --slave_pass=xxx
  50. Sun May 24 18:32:06 2020 - [info]   Connecting to root@192.168.28.132(192.168.28.132:22)..
  51.   Checking slave recovery environment settings..
  52.     Opening /data/mysql3306/data/relay-log.info ... ok.
  53.     Relay log found at /data/mysql3306/data, up to relay-log.000005
  54.     Temporary relay log file is /data/mysql3306/data/relay-log.000005
  55.     Checking if super_read_only is defined and turned on.. not present or turned off, ignoring.
  56.     Testing mysql connection and privileges.
  57. mysql: [Warning] Using a password on the command line interface can be insecure.
  58.  done.
  59.     Testing mysqlbinlog output.. done.
  60.     Cleaning up test file(s).. done.
  61. Sun May 24 18:32:07 2020 - [info] Slaves settings check done.
  62. Sun May 24 18:32:07 2020 - [info]
  63. 192.168.28.128(192.168.28.128:3306) (current master)
  64.  +--192.168.28.131(192.168.28.131:3306)
  65.  +--192.168.28.132(192.168.28.132:3306)
  66.  
  67. Sun May 24 18:32:07 2020 - [info] Checking master_ip_failover_script status:
  68. Sun May 24 18:32:07 2020 - [info]   /usr/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.28.128 --orig_master_ip=192.168.28.128 --orig_master_port=3306
  69.  
  70. IN SCRIPT TEST====/sbin/ip addr del 192.168.28.199/24 dev ens33==/sbin/ip addr add  192.168.28.199/24 dev  ens33===
  71.  
  72. Checking the Status of the script.. OK
  73. Sun May 24 18:32:08 2020 - [info]  OK.
  74. Sun May 24 18:32:08 2020 - [warning] shutdown_script is not defined.
  75. Sun May 24 18:32:08 2020 - [info] Set master ping interval 3 seconds.
  76. Sun May 24 18:32:08 2020 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
  77. Sun May 24 18:32:08 2020 - [info] Starting ping health check on 192.168.28.128(192.168.28.128:3306)..
  78. Sun May 24 18:32:08 2020 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

3.2  测试自动切换

模拟主库数据库down

主库执行shutdown

  1. mysql> shutdown;

观察日志：

日志中大致的流程是检测到主库（192.168.28.128:3306）不可用-->连续试探3次（次数可自定义）-->检测进群中剩余存活的节点-->从备选主节点中选择一个节点为主节点-->漂移VIP至新的主节点（如果原主节点系统正常则将VIP在原主机上删除）-->拷贝原主节点的binlog日志-->新主节点判断是否需要补充日志-->其他节点全部改为从新主节点复制数据（组成新的集群）

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

此时的VIP在 192.168.28.131机器上了

原主节点已删掉该VIP

3.3 手动切换测试

将原主节点恢复并加入集群，保证集群3个节点在线

  1. [root@mha1 masterha]# /usr/local/mysql5.7/bin/mysqld_safe  --defaults-file=/data/mysql3306/etc/my.cnf  &
  2.  
  3. [root@mha1 masterha]# mysql -uroot -p'' --socket=/data/mysql3306/tmp/mysql.sock
  4.  
  5. change master to master_host='192.168.28.131',master_user='repl', master_password='repl',master_log_file='mysql-bin.000008',master_log_pos=154;  /*生产环境的恢复建议备份主库再配置同步*/

此时再检测集群状态

  1. [root@mha3 app1]# masterha_check_repl --conf=/etc/masterha/app1.conf

手动切换主库

很多时候需要主动进行主从切换，此时就可以用MHA的手动切换脚本来进行，例如将主库再切回192.168.28.128:3306上（此时MHA如果是启动状态则必须关闭）

  1. masterha_master_switch  --conf=/etc/masterha/app1.conf --master_state=alive  --orig_master_is_new_slave --new_master_host=192.168.28.128 --new_master_port=3306

切换过程如下：

  1. [root@mha3 app1]# masterha_master_switch  --conf=/etc/masterha/app1.conf --master_state=alive  --orig_master_is_new_slave --new_master_host=192.168.28.128 --new_master_port=3306
  2. Sun May 24 19:10:29 2020 - [info] MHA::MasterRotate version 0.58.
  3. Sun May 24 19:10:29 2020 - [info] Starting online master switch..
  4. Sun May 24 19:10:29 2020 - [info]
  5. Sun May 24 19:10:29 2020 - [info] * Phase 1: Configuration Check Phase..
  6. Sun May 24 19:10:29 2020 - [info]
  7. Sun May 24 19:10:29 2020 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
  8. Sun May 24 19:10:29 2020 - [info] Reading application default configuration from /etc/masterha/app1.conf..
  9. Sun May 24 19:10:29 2020 - [info] Reading server configuration from /etc/masterha/app1.conf..
  10. Sun May 24 19:10:30 2020 - [info] GTID failover mode = 0
  11. Sun May 24 19:10:30 2020 - [info] Current Alive Master: 192.168.28.131(192.168.28.131:3306)
  12. Sun May 24 19:10:30 2020 - [info] Alive Slaves:
  13. Sun May 24 19:10:30 2020 - [info]   192.168.28.128(192.168.28.128:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  14. Sun May 24 19:10:30 2020 - [info]     Replicating from 192.168.28.131(192.168.28.131:3306)
  15. Sun May 24 19:10:30 2020 - [info]     Primary candidate for the new Master (candidate_master is set)
  16. Sun May 24 19:10:30 2020 - [info]   192.168.28.132(192.168.28.132:3306)  Version=5.7.25-28-log (oldest major version between slaves) log-bin:enabled
  17. Sun May 24 19:10:30 2020 - [info]     Replicating from 192.168.28.131(192.168.28.131:3306)
  18. Sun May 24 19:10:30 2020 - [info]     Not candidate for the new Master (no_master is set)
  19.  
  20. It is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 192.168.28.131(192.168.28.131:3306)? (YES/no): yes
  21. Sun May 24 19:10:32 2020 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..
  22. Sun May 24 19:10:32 2020 - [info]  ok.
  23. Sun May 24 19:10:32 2020 - [info] Checking MHA is not monitoring or doing failover..
  24. Sun May 24 19:10:32 2020 - [info] Checking replication health on 192.168.28.128..
  25. Sun May 24 19:10:32 2020 - [info]  ok.
  26. Sun May 24 19:10:32 2020 - [info] Checking replication health on 192.168.28.132..
  27. Sun May 24 19:10:32 2020 - [info]  ok.
  28. Sun May 24 19:10:32 2020 - [info] 192.168.28.128 can be new master.
  29. Sun May 24 19:10:32 2020 - [info]
  30. From:
  31. 192.168.28.131(192.168.28.131:3306) (current master)
  32.  +--192.168.28.128(192.168.28.128:3306)
  33.  +--192.168.28.132(192.168.28.132:3306)
  34.  
  35. To:
  36. 192.168.28.128(192.168.28.128:3306) (new master)
  37.  +--192.168.28.132(192.168.28.132:3306)
  38.  +--192.168.28.131(192.168.28.131:3306)
  39.  
  40. Starting master switch from 192.168.28.131(192.168.28.131:3306) to 192.168.28.128(192.168.28.128:3306)? (yes/NO): yes
  41. Sun May 24 19:10:33 2020 - [info] Checking whether 192.168.28.128(192.168.28.128:3306) is ok for the new master..
  42. Sun May 24 19:10:33 2020 - [info]  ok.
  43. Sun May 24 19:10:33 2020 - [info] 192.168.28.131(192.168.28.131:3306): SHOW SLAVE STATUS returned empty result. To check replication filtering rules, temporarily executing CHANGE MASTER to a dummy host.
  44. Sun May 24 19:10:33 2020 - [info] 192.168.28.131(192.168.28.131:3306): Resetting slave pointing to the dummy host.
  45. Sun May 24 19:10:33 2020 - [info] ** Phase 1: Configuration Check Phase completed.
  46. Sun May 24 19:10:33 2020 - [info]
  47. Sun May 24 19:10:33 2020 - [info] * Phase 2: Rejecting updates Phase..
  48. Sun May 24 19:10:33 2020 - [info]
  49. Sun May 24 19:10:33 2020 - [info] Executing master ip online change script to disable write on the current master:
  50. Sun May 24 19:10:33 2020 - [info]   /usr/bin/master_ip_online_change --command=stop --orig_master_host=192.168.28.131 --orig_master_ip=192.168.28.131 --orig_master_port=3306 --orig_master_user='mha' --new_master_host=192.168.28.128 --new_master_ip=192.168.28.128 --new_master_port=3306 --new_master_user='mha' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
  51.  
  52. IN SCRIPT TEST====/sbin/ip addr del 192.168.28.199/24 dev ens33==/sbin/ip addr add 192.168.28.199/24 dev ens33===
  53.  
  54. Disabling the VIP on old master: 192.168.28.131
  55. Sun May 24 19:10:33 2020 - [info]  ok.
  56. Sun May 24 19:10:33 2020 - [info] Locking all tables on the orig master to reject updates from everybody (including root):
  57. Sun May 24 19:10:33 2020 - [info] Executing FLUSH TABLES WITH READ LOCK..
  58. Sun May 24 19:10:33 2020 - [info]  ok.
  59. Sun May 24 19:10:33 2020 - [info] Orig master binlog:pos is mysql-bin.000008:154.
  60. Sun May 24 19:10:33 2020 - [info]  Waiting to execute all relay logs on 192.168.28.128(192.168.28.128:3306)..
  61. Sun May 24 19:10:33 2020 - [info]  master_pos_wait(mysql-bin.000008:154) completed on 192.168.28.128(192.168.28.128:3306). Executed 0 events.
  62. Sun May 24 19:10:33 2020 - [info]   done.
  63. Sun May 24 19:10:33 2020 - [info] Getting new master's binlog name and position..
  64. Sun May 24 19:10:33 2020 - [info]  mysql-bin.000014:154
  65. Sun May 24 19:10:33 2020 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.28.128', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000014', MASTER_LOG_POS=154, MASTER_USER='repl', MASTER_PASSWORD='xxx';
  66. Sun May 24 19:10:33 2020 - [info] Executing master ip online change script to allow write on the new master:
  67. Sun May 24 19:10:33 2020 - [info]   /usr/bin/master_ip_online_change --command=start --orig_master_host=192.168.28.131 --orig_master_ip=192.168.28.131 --orig_master_port=3306 --orig_master_user='mha' --new_master_host=192.168.28.128 --new_master_ip=192.168.28.128 --new_master_port=3306 --new_master_user='mha' --orig_master_ssh_user=root --new_master_ssh_user=root   --orig_master_is_new_slave --orig_master_password=xxx --new_master_password=xxx
  68.  
  69. IN SCRIPT TEST====/sbin/ip addr del 192.168.28.199/24 dev ens33==/sbin/ip addr add 192.168.28.199/24 dev ens33===
  70.  
  71. Enabling the VIP - 192.168.28.199/24 on the new master - 192.168.28.128
  72. Sun May 24 19:10:34 2020 - [info]  ok.
  73. Sun May 24 19:10:34 2020 - [info] Setting read_only=0 on 192.168.28.128(192.168.28.128:3306)..
  74. Sun May 24 19:10:34 2020 - [info]  ok.
  75. Sun May 24 19:10:34 2020 - [info]
  76. Sun May 24 19:10:34 2020 - [info] * Switching slaves in parallel..
  77. Sun May 24 19:10:34 2020 - [info]
  78. Sun May 24 19:10:34 2020 - [info] -- Slave switch on host 192.168.28.132(192.168.28.132:3306) started, pid: 49178
  79. Sun May 24 19:10:34 2020 - [info]
  80. Sun May 24 19:10:35 2020 - [info] Log messages from 192.168.28.132 ...
  81. Sun May 24 19:10:35 2020 - [info]
  82. Sun May 24 19:10:34 2020 - [info]  Waiting to execute all relay logs on 192.168.28.132(192.168.28.132:3306)..
  83. Sun May 24 19:10:34 2020 - [info]  master_pos_wait(mysql-bin.000008:154) completed on 192.168.28.132(192.168.28.132:3306). Executed 0 events.
  84. Sun May 24 19:10:34 2020 - [info]   done.
  85. Sun May 24 19:10:34 2020 - [info]  Resetting slave 192.168.28.132(192.168.28.132:3306) and starting replication from the new master 192.168.28.128(192.168.28.128:3306)..
  86. Sun May 24 19:10:34 2020 - [info]  Executed CHANGE MASTER.
  87. Sun May 24 19:10:34 2020 - [info]  Slave started.
  88. Sun May 24 19:10:35 2020 - [info] End of log messages from 192.168.28.132 ...
  89. Sun May 24 19:10:35 2020 - [info]
  90. Sun May 24 19:10:35 2020 - [info] -- Slave switch on host 192.168.28.132(192.168.28.132:3306) succeeded.
  91. Sun May 24 19:10:35 2020 - [info] Unlocking all tables on the orig master:
  92. Sun May 24 19:10:35 2020 - [info] Executing UNLOCK TABLES..
  93. Sun May 24 19:10:35 2020 - [info]  ok.
  94. Sun May 24 19:10:35 2020 - [info] Starting orig master as a new slave..
  95. Sun May 24 19:10:35 2020 - [info]  Resetting slave 192.168.28.131(192.168.28.131:3306) and starting replication from the new master 192.168.28.128(192.168.28.128:3306)..
  96. Sun May 24 19:10:35 2020 - [info]  Executed CHANGE MASTER.
  97. Sun May 24 19:10:35 2020 - [info]  Slave started.
  98. Sun May 24 19:10:35 2020 - [info] All new slave servers switched successfully.
  99. Sun May 24 19:10:35 2020 - [info]
  100. Sun May 24 19:10:35 2020 - [info] * Phase 5: New master cleanup phase..
  101. Sun May 24 19:10:35 2020 - [info]
  102. Sun May 24 19:10:35 2020 - [info]  192.168.28.128: Resetting slave info succeeded.
  103. Sun May 24 19:10:35 2020 - [info] Switching master to 192.168.28.128(192.168.28.128:3306) completed successfully.

此时查看，主库已切回192.168.28.128:3306节点上了。

4  补充

配置2个定时任务，分别用于清理relay-log及服务器时钟同步,每台机器上均配置

清理relay-log

因MHA集群建议关闭relay-log 所以relay-log需要手动清理，因此可以配置一个定时任务进行清理

  1. 00 01 * * 0 /usr/bin/purge_relay_logs --user=mha --password='MHAadmin123' --host=192.168.28.131' --disable_relay_log_purge >> /var/log/masterha/app1/purge_relay_logs.log 2>&1

配置时钟同步

可以配置公网的时钟服务器，也可以自己搭建（生产环境需有自建的时钟服务器，可以参考 时钟服务器搭建）

  1. */15  *  * * *   /usr/sbin/ntpdate  ntp1.aliyun.com; /sbin/hwclock -w

5  小结

MHA的搭建过程中最大的困难点在于经常依赖包安装不全以及相关脚本与版本不对应导致一直无法部署，还有一个问题是集群复制检查、手动切换主库均正常，但是主库异常宕机时无法切换（切换脚本问题）。小伙伴们在实践过程中遇到问题可以多多与我沟通，相互学习提高排坑技能。如需相关安装软件及依赖包也可以关注公众号 数据库干货铺 联系我获取或回复“加群”进入技术交流群与更多小伙伴交流。

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. 高可用,完全分布式Hadoop集群HDFS和MapReduce安装配置指南

    原文:http://my.oschina.net/wstone/blog/365010#OSC_h3_13 (WJW)高可用,完全分布式Hadoop集群HDFS和MapReduce安装配置指南 [X] ...

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

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

  5. 【线上测试之后的应用】基于MySQL+MHA+Haproxy构建高可用负载均衡数据库集群（详解）

    这里我们先介绍一下MHA是什么,其次就是它的应用与测试,同时为了大家呈现了数据备份案例,最后总结了使用情况以及注意事项和解决办法 一.MHA 概述 MHA(Master High Availabili ...

  6. MySQL高可用架构之MHA

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

  7. Linux 高可用（HA）集群之keepalived详解

    http://freeloda.blog.51cto.com/2033581/1280962 大纲 一.前言 二.Keepalived 详解 三.环境准备 四.LVS+Keepalived 实现高可用 ...

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

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

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

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

随机推荐

  1. CultureInfo 类中需要的【区域性名称】查询

    2019独角兽企业重金招聘Python工程师标准>>> 提供有关特定区域性的信息(对于非托管代码开发,则称为"区域设置"). 这些信息包括区域性的名称.书写系统. ...

  2. 信息竞赛进阶指南--区间最值问题的ST算法

    void ST_prework() { for (int i = 1; i <= n; i++) f[i][0] = a[i]; int t = log(n) / log(2) + 1; for ...

  3. USACO Training Section 1.2 [USACO1.2]方块转换 Transformations

    题目描述 一块N x N(1<=N<=10)正方形的黑白瓦片的图案要被转换成新的正方形图案.写一个程序来找出将原始图案按照以下列转换方法转换成新图案的最小方式: 1:转90度:图案按顺时针 ...

  4. JavaScript键值对集合怎么使用

    JavaScript键值对集合怎么使用 我们可以对此键值对集合分为3种难度 1.简单的使用 var arr = { 'cn': "中国", 'usa': '美国', 'jp': ' ...

  5. D. Sequence Sorting dp

    D. Sequence Sorting 题目大意:给你一个序列,有一种操作就是对所有相同的数可以挪到最前面,也可以挪到最后面,问最少操作次数. 首先,对于很多个相同的数,可以缩成两个位置,一个是就是这 ...

  6. I - Coins dp

    http://acm.hdu.edu.cn/showproblem.php?pid=2844 这个题目是一个多重背包转化成01背包 题意: Whuacmers拥有bi个面值为ai的硬币,现在他要用这些 ...

  7. SpringData Redis的简单使用

    SpringDate Redis是在Jedis框架的基础之上对Redis进行了高度封装,通过简单的属性配置就可以通过调用方法完成对Redis数据库的操作,而且SpringData Redis使用了连接 ...

  8. 在web项目中使用shiro（认证、授权）

    一.在web项目中实现认证 第一步,在web项目中导入shiro依赖的包 第二步,在web.xml中声明shiro拦截权限的过滤器 <filter> <filter-name> ...

  9. while(scanf("%d",&n)!=EOF) / while(cin>>n)终止问题

    问题的发现:(想要看干货可以直接跳过这段) 我最近刚了解到关于栈的用法,于是按照参考书寻找代码,并把它敲到电脑上.编译运行代码后发现无法终止,在网上查找各种资料,总结如下. 因为我的电脑是Window ...

  10. LeetCode--Array--Remove Duplicates from Sorted Array (Easy)

    26. Remove Duplicates from Sorted Array (Easy) Given a sorted array nums, remove the duplicates in-p ...