sky_cheng

linux下mysql5.7的MHA高可用架构搭建

一、MHA简介

MHA（Master High Availability）目前在mysql高可用方面比较成熟。是一套优秀的作为 mysql高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA 能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA 能在最大程度上保证数据的一致性，以达到真正意义上的高可用。

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

二、架构

172.28.18.71作为MHA管理节点，负责管理Mysql主从集群，172.28.18.69为Mysql主库，172.28.18.78为Mysql从库，172.28.18.71也是mysql的一个从库,172.28.18.70为虚拟IP

二、三台服务器均安装mysql5.7,并设置好主从GTID复制模式

参照:https://www.cnblogs.com/sky-cheng/p/10955054.html

三、设置3台服务器ssh免密登陆

1、在172.28.18.71上操作生成ssh key

[root@localhost /]# cd
[root@localhost ~]# pwd
/root

进入root目录，执行下面命令，生成ssh key

[root@localhost ~]# ssh-keygen 
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa): 
Created directory '/root/.ssh'.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
SHA256:wesmi4cYtji2OdL2cBpIpnEAITXtNmCg6MYvYyrKSFw [email protected]
The key's randomart image is:
+---[RSA 2048]----+
|=+o.             |
|= o..  .         |
|+. o    o        |
|o.  +    o       |
|.*.E .  S        |
|*+=    .         |
|oXo=... o        |
|@oO=...+         |
|O*+.o..          |
+----[SHA256]-----+

2、此时在 /root/.ssh/下面生成一个id_rsa.pub文件，复制为authorized_keys

[root@localhost .ssh]# cp id_rsa.pub authorized_keys
[root@localhost .ssh]# ll
总用量 12
-rw-r--r-- 1 root root  408 6月   4 14:06 authorized_keys
-rw------- 1 root root 1679 6月   4 14:02 id_rsa
-rw-r--r-- 1 root root  408 6月   4 14:02 id_rsa.pub

3、将.ssh目录复制到另外两个节点的/root下

[root@localhost ~]# scp -P25601 -r /root/.ssh/ root@172.28.18.69:/root/
The authenticity of host '[172.28.18.69]:25601 ([172.28.18.69]:25601)' can't be established.
ECDSA key fingerprint is SHA256:u5esiwOe7+3IGRBM9BOWYFMqe873DqimVeGBT2+nHdg.
ECDSA key fingerprint is MD5:d3:05:0a:9d:92:46:7d:1c:ab:74:24:4b:cd:ae:81:b5.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[172.28.18.69]:25601' (ECDSA) to the list of known hosts.
root@172.28.18.69's password: 
id_rsa                                                                             100% 1679   152.5KB/s   00:00    
id_rsa.pub                                                                         100%  408    80.3KB/s   00:00    
authorized_keys                                                                    100%  408    51.6KB/s   00:00    
known_hosts                                                                        100%  182    35.6KB/s   00:00

[root@localhost ~]# scp -P25601 -r /root/.ssh/ root@172.28.18.78:/root/
The authenticity of host '[172.28.18.78]:25601 ([172.28.18.78]:25601)' can't be established.
ECDSA key fingerprint is SHA256:zsVfyGQ5sza1SvWg/2wCqf4SVHMsLKXYkt4QlxE+sU4.
ECDSA key fingerprint is MD5:78:13:37:ab:18:a9:b0:67:3d:0f:22:53:e6:ac:b5:62.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '[172.28.18.78]:25601' (ECDSA) to the list of known hosts.
root@172.28.18.78's password: 
id_rsa                                                                             100% 1679   190.0KB/s   00:00    
id_rsa.pub                                                                         100%  408    55.0KB/s   00:00    
authorized_keys                                                                    100%  408    53.2KB/s   00:00    
known_hosts                                                                        100%  364   378.8KB/s   00:00    
[root@localhost ~]#

4、ssh免密登陆测试

[root@localhost ~]# ssh 172.28.18.69 -p 25601
Last login: Tue Jun  4 14:13:32 2019 from 172.28.18.71
[root@server-1 ~]# exit
登出
Connection to 172.28.18.69 closed.
[root@localhost ~]# ssh 172.28.18.78 -p 25601
Last login: Tue Jun  4 14:13:39 2019 from 172.28.18.71
[root@server-2 ~]# exit
登出
Connection to 172.28.18.78 closed.
[root@localhost ~]#

四、三台服务器均安装MHA的node节点

1、下载mha的node源码包

[root@localhost ~]# mkdir /usr/local/src/mha4mysql-node
[root@localhost ~]# cd /usr/local/src/mha4mysql-node

[root@localhost mha4mysql-node]# wget https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.58/mha4mysql-node-0.58.tar.gz
--2019-06-04 14:28:19-- https://github.com/yoshinorim/mha4mysql-node/releases/download/v0.58/mha4mysql-node-0.58.tar.gz
正在解析主机 github.com (github.com)... 13.250.177.223
正在连接 github.com (github.com)|13.250.177.223|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 302 Found
位置：https://github-production-release-asset-2e65be.s3.amazonaws.com/2093258/9d78fb60-2de4-11e8-8f0c-bac507a4e54f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190604%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190604T062830Z&X-Amz-Expires=300&X-Amz-Signature=ed981fb367ad8bde9852881a5336f8af1a8927afcb797a6c9eddf41f5678fd75&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dmha4mysql-node-0.58.tar.gz&response-content-type=application%2Foctet-stream [跟随至新的 URL]
--2019-06-04 14:28:30-- https://github-production-release-asset-2e65be.s3.amazonaws.com/2093258/9d78fb60-2de4-11e8-8f0c-bac507a4e54f?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20190604%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20190604T062830Z&X-Amz-Expires=300&X-Amz-Signature=ed981fb367ad8bde9852881a5336f8af1a8927afcb797a6c9eddf41f5678fd75&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dmha4mysql-node-0.58.tar.gz&response-content-type=application%2Foctet-stream
正在解析主机 github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)... 52.216.18.168
正在连接 github-production-release-asset-2e65be.s3.amazonaws.com (github-production-release-asset-2e65be.s3.amazonaws.com)|52.216.18.168|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 200 OK
长度：56220 (55K) [application/octet-stream]
正在保存至: “mha4mysql-node-0.58.tar.gz”

100%[===========================================================================>] 56,220 47.8KB/s 用时 1.1s

2019-06-04 14:28:32 (47.8 KB/s) - 已保存 “mha4mysql-node-0.58.tar.gz” [56220/56220])

2、安装perl-DBD-MySQL

[root@localhost mha4mysql-node]# yum install perl-DBD-MySQL -y
[root@localhost mha4mysql-node]# yum install perl-DBI -y
[root@localhost mha4mysql-node]# yum install mysql-libs -y

3、解压、编译

[root@localhost mha4mysql-node]# tar -zxvf mha4mysql-node-0.58.tar.gz
drwxr-xr-x 2 zabbix zabbix    49 3月  23 2018 t
[root@localhost mha4mysql-node-0.58]# perl Makefile.PL 
Can't locate ExtUtils/MakeMaker.pm in @INC (@INC contains: inc /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at inc/Module/Install/Can.pm line 5.

报错，不能定位ExtUtils,怎安装ExtUtils-MakeMaker

[root@localhost src]# mkdir /usr/local/src/ExtUtils-MakeMaker
[root@localhost src]# cd ExtUtils-MakeMaker/
[root@localhost ExtUtils-MakeMaker]# wget http://files.directadmin.com/services/9.0/ExtUtils-MakeMaker-6.31.tar.gz

[root@localhost ExtUtils-MakeMaker]# tar -zxvf ExtUtils-MakeMaker-6.31.tar.gz 
[root@localhost ExtUtils-MakeMaker]# cd ExtUtils-MakeMaker-6.31
[root@localhost ExtUtils-MakeMaker-6.31]# perl Makefile.PL 
Checking if your kit is complete...
Looks good
Could not open '': 没有那个文件或目录 at lib/ExtUtils/MM_Unix.pm line 2697.

报错，则安装perl-ExtUtils-MakeMaker

[root@localhost ExtUtils-MakeMaker-6.31]# yum install perl-ExtUtils-MakeMaker

再次编译

[root@localhost ExtUtils-MakeMaker-6.31]# perl Makefile.PL 
Checking if your kit is complete...
Looks good
Writing Makefile for ExtUtils::MakeMaker
[root@localhost ExtUtils-MakeMaker-6.31]#

成功，继续make make install

[root@localhost ExtUtils-MakeMaker-6.31]# make && make install

ExtUtils-MakeMaker安装成功后，再次编译mha4mysql-node

[root@localhost mha4mysql-node-0.58]# cd /usr/local/src/mha4mysql-node/mha4mysql-node-0.58
[root@localhost mha4mysql-node-0.58]# perl Makefile.PL 
*** Module::AutoInstall version 1.06
*** Checking for Perl dependencies...
Can't locate CPAN.pm in @INC (@INC contains: inc /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at inc/Module/AutoInstall.pm line 304.

提示找不到CPAN.pm,则安装CPAN模块

[root@localhost mha4mysql-node-0.58]# mkdir /usr/local/src/CPAN
[root@localhost mha4mysql-node-0.58]# cd /usr/local/src/CPAN/
[root@localhost CPAN]# wget http://search.cpan.org/CPAN/authors/id/A/AN/ANDK/CPAN-1.9205.tar.gz
[root@localhost CPAN]# tar -zxvf CPAN-1.9205.tar.gz 
[root@localhost CPAN]# cd CPAN-1.9205
[root@localhost CPAN-1.9205]# perl Makefile.PL 
Importing PAUSE public key into your GnuPG keychain... gpg: 新的配置文件‘/root/.gnupg/gpg.conf’已建立
gpg: 警告：在‘/root/.gnupg/gpg.conf’里的选项于此次运行期间未被使用
done!
(You may wish to trust it locally with 'gpg --lsign-key 450F89EC')
WARNING: EXTRA_META is not a known parameter.
Checking if your kit is complete...
Looks good
Warning: prerequisite Test::More 0 not found.
'EXTRA_META' is not a known MakeMaker parameter name.
Writing Makefile for CPAN
[root@localhost CPAN-1.9205]# make && make install

再次编译mha4mysql-node

[root@server-1 CPAN-1.9205]# cd /usr/local/src/mha4mysql-node/mha4mysql-node-0.58
[root@localhost mha4mysql-node-0.58]# perl Makefile.PL 
*** Module::AutoInstall version 1.06
*** Checking for Perl dependencies...
[Core Features]
- DBI        ...loaded. (1.627)
- DBD::mysql ...loaded. (4.023)
*** Module::AutoInstall configuration finished.
Checking if your kit is complete...
Looks good
Writing Makefile for mha4mysql::node
[root@localhost mha4mysql-node-0.58]#

成功，继续make && make install

[root@localhost mha4mysql-node-0.58]# make && make install

另外两台服务器也同样安装mha4mysql-node

五、管理节点安装mha4mysql-manager

[root@localhost mha4mysql-node-0.58] yum install -y perl-Mail-Sender perl-Email-Date-Format perl-MIME-Types perl-MIME-Lite perl-Parallel-ForkManager perl-Mail-Sendmail

[root@localhost mha4mysql-node-0.58] yum install -y perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-YAML-Tiny perl-PAR-Dist perl-Module-ScanDeps perl-Module-CoreList perl-Module-Build perl-CPAN perl-YAML perl-CPANPLUS perl-File-Remove perl-Module-Install
[root@localhost masterha]# cpan Module::Install
[root@localhost src]# perl -MCPAN -e "install Class::Load"

[root@localhost mha4mysql-node-0.58]# mkdir /usr/local/src/mha4mysql-manager
[root@localhost mha4mysql-node-0.58]# cd /usr/local/src/mha4mysql-manager
[root@localhost mha4mysql-manager]# wget https://github.com/yoshinorim/mha4mysql-manager/releases/download/v0.58/mha4mysql-manager-0.58.tar.gz
[root@localhost mha4mysql-manager]# tar -zxvf mha4mysql-manager-0.58.tar.gz 
[root@localhost mha4mysql-manager]# cd mha4mysql-manager-0.58

[root@localhost mha4mysql-manager-0.58]# perl Makefile.PL
*** Module::AutoInstall version 1.06
*** Checking for Perl dependencies...
[Core Features]
- DBI ...loaded. (1.627)
- DBD::mysql ...loaded. (4.023)
- Time::HiRes ...loaded. (1.9725)
- Config::Tiny ...loaded. (2.14)
- Log::Dispatch ...loaded. (2.41)
- Parallel::ForkManager ...loaded. (2.02)
- MHA::NodeConst ...loaded. (0.58)
*** Module::AutoInstall configuration finished.
Writing Makefile for mha4mysql::manager
Writing MYMETA.yml and MYMETA.json
[root@localhost mha4mysql-manager-0.58]#

make && make install

[root@server-1 mha4mysql-node-0.58]# make && make install

查看结果

[root@localhost bin]# ll /usr/local/bin/masterha_*
-r-xr-xr-x 1 root root 1995 6月   4 16:26 /usr/local/bin/masterha_check_repl
-r-xr-xr-x 1 root root 1779 6月   4 16:26 /usr/local/bin/masterha_check_ssh
-r-xr-xr-x 1 root root 1865 6月   4 16:26 /usr/local/bin/masterha_check_status
-r-xr-xr-x 1 root root 3201 6月   4 16:26 /usr/local/bin/masterha_conf_host
-r-xr-xr-x 1 root root 2517 6月   4 16:26 /usr/local/bin/masterha_manager
-r-xr-xr-x 1 root root 2165 6月   4 16:26 /usr/local/bin/masterha_master_monitor
-r-xr-xr-x 1 root root 2373 6月   4 16:26 /usr/local/bin/masterha_master_switch
-r-xr-xr-x 1 root root 5172 6月   4 16:26 /usr/local/bin/masterha_secondary_check
-r-xr-xr-x 1 root root 1739 6月   4 16:26 /usr/local/bin/masterha_stop

masterha_check_ssh 检查MHA的SSH配置状况

masterha_check_repl 检查MySQL复制状况

masterha_manger 启动MHA

masterha_check_status 检测当前MHA运行状态

masterha_master_monitor 检测master是否宕机

masterha_master_switch 控制故障转移（自动或者手动）

masterha_conf_host 添加或删除配置的server信息

六、编写管理节点配置文件

[root@localhost ~]# mkdir /etc/masterha
[root@localhost ~]# cd /etc/masterha/
[root@localhost masterha]# vim app1.cnf
[server default]
manager_workdir=/etc/mha
manager_log=/etc/mha/manager.log
#mysql用户和密码
password=Zaq1xsw@
user=root
#监控主库，发送ping包的时间间隔，默认是3秒，尝试3次不成功，则自动进行切换操作
ping_interval=1
#复制用户
repl_password=Zaq1xsw@
repl_user=repl
#report_script=/usr/local/send_report

#通过第三方机器确认目标主库是否存活,不是必须的,就算没有也是能用

#secondary_check_script=masterha_secondary_check -s 172.28.18.71 -s 172.28.18.69 -s 172.28.18.78

#故障自动切换VIP调用脚本,不是必须的,就算没有也是能用,

master_ip_failover_script=/etc/masterha/scripts/master_ip_failover

#ssh用户
ssh_user=root
ssh_port=25601

[server1]
hostname=172.28.18.71
candidate_master=1

[server2]
hostname=172.28.18.69 
candidate_master=1 

[server3] 
hostname=172.28.18.78 
candidate_master=1

七、检查ssh连接

root@localhost ~]

[root@localhost mysql-5.7.26]# masterha_check_ssh --conf=/etc/masterha/app1.cnf 
Thu Jun  6 14:11:16 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Jun  6 14:11:16 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Thu Jun  6 14:11:16 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Thu Jun  6 14:11:16 2019 - [info] Starting SSH connection tests..
Thu Jun  6 14:11:19 2019 - [debug] 
Thu Jun  6 14:11:16 2019 - [debug]  Connecting via SSH from root@172.28.18.71(172.28.18.71:25601) to root@172.28.18.69(172.28.18.69:25601)..
Thu Jun  6 14:11:18 2019 - [debug]   ok.
Thu Jun  6 14:11:18 2019 - [debug]  Connecting via SSH from root@172.28.18.71(172.28.18.71:25601) to root@172.28.18.78(172.28.18.78:25601)..
Thu Jun  6 14:11:18 2019 - [debug]   ok.
^[[AThu Jun  6 14:11:29 2019 - [debug] 
Thu Jun  6 14:11:17 2019 - [debug]  Connecting via SSH from root@172.28.18.78(172.28.18.78:25601) to root@172.28.18.71(172.28.18.71:25601)..
Thu Jun  6 14:11:23 2019 - [debug]   ok.
Thu Jun  6 14:11:23 2019 - [debug]  Connecting via SSH from root@172.28.18.78(172.28.18.78:25601) to root@172.28.18.69(172.28.18.69:25601)..
Thu Jun  6 14:11:28 2019 - [debug]   ok.
Thu Jun  6 14:11:29 2019 - [debug] 
Thu Jun  6 14:11:17 2019 - [debug]  Connecting via SSH from root@172.28.18.69(172.28.18.69:25601) to root@172.28.18.71(172.28.18.71:25601)..
Thu Jun  6 14:11:22 2019 - [debug]   ok.
Thu Jun  6 14:11:22 2019 - [debug]  Connecting via SSH from root@172.28.18.69(172.28.18.69:25601) to root@172.28.18.78(172.28.18.78:25601)..
Thu Jun  6 14:11:28 2019 - [debug]   ok.
Thu Jun  6 14:11:29 2019 - [info] All SSH connection tests passed successfully.

测试成功

八、检查复制

[root@localhost mysql-5.7.26]# masterha_check_repl --conf=/etc/masterha/app1.cnf 
Thu Jun  6 13:54:14 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Jun  6 13:54:14 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Thu Jun  6 13:54:14 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Thu Jun  6 13:54:14 2019 - [info] MHA::MasterMonitor version 0.58.
Thu Jun  6 13:54:15 2019 - [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.
Compilation failed in require at (eval 55) line 3.

 at /usr/local/share/perl5/MHA/DBHelper.pm line 208.
 at /usr/local/share/perl5/MHA/Server.pm line 166.
Thu Jun  6 13:54:15 2019 - [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln301] install_driver(mysql) failed: Attempt to reload DBD/mysql.pm aborted.
Compilation failed in require at (eval 55) line 3.

 at /usr/local/share/perl5/MHA/DBHelper.pm line 208.
 at /usr/local/share/perl5/MHA/Server.pm line 166.
Thu Jun  6 13:54:16 2019 - [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln309] Got fatal error, stopping operations
Thu Jun  6 13:54:16 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations.  at /usr/local/share/perl5/MHA/MasterMonitor.pm line 329.
Thu Jun  6 13:54:16 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Thu Jun  6 13:54:16 2019 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

报错，此时检查是否安装了perl-DBD-mysql

[root@localhost mysql-5.7.26]# yum install perl-DBD-MySQL
已加载插件：fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.huaweicloud.com
 * epel: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
正在解决依赖关系
--> 正在检查事务
---> 软件包 perl-DBD-MySQL.x86_64.0.4.023-6.el7 将被 安装
--> 正在处理依赖关系 libmysqlclient.so.18(libmysqlclient_18)(64bit)，它被软件包 perl-DBD-MySQL-4.023-6.el7.x86_64 需要
--> 正在处理依赖关系 libmysqlclient.so.18()(64bit)，它被软件包 perl-DBD-MySQL-4.023-6.el7.x86_64 需要
--> 正在检查事务
---> 软件包 mariadb-libs.x86_64.1.5.5.60-1.el7_5 将被 安装
Removing mariadb-libs.x86_64 1:5.5.60-1.el7_5 - u due to obsoletes from installed mysql-community-libs-5.7.26-1.el7.x86_64
base/7/x86_64/filelists_db                                                                            | 7.1 MB  00:00:03     
--> 正在使用新的信息重新解决依赖关系
--> 正在检查事务
---> 软件包 mariadb-libs.x86_64.1.5.5.60-1.el7_5 将被 安装
--> 正在处理依赖关系 libmysqlclient.so.18(libmysqlclient_18)(64bit)，它被软件包 perl-DBD-MySQL-4.023-6.el7.x86_64 需要
--> 正在处理依赖关系 libmysqlclient.so.18(libmysqlclient_18)(64bit)，它被软件包 2:postfix-2.10.1-7.el7.x86_64 需要
--> 正在处理依赖关系 libmysqlclient.so.18()(64bit)，它被软件包 perl-DBD-MySQL-4.023-6.el7.x86_64 需要
--> 正在处理依赖关系 libmysqlclient.so.18()(64bit)，它被软件包 2:postfix-2.10.1-7.el7.x86_64 需要
--> 解决依赖关系完成
错误：软件包：perl-DBD-MySQL-4.023-6.el7.x86_64 (base)
          需要：libmysqlclient.so.18(libmysqlclient_18)(64bit)
错误：软件包：2:postfix-2.10.1-7.el7.x86_64 (@anaconda)
          需要：libmysqlclient.so.18(libmysqlclient_18)(64bit)
错误：软件包：2:postfix-2.10.1-7.el7.x86_64 (@anaconda)
          需要：libmysqlclient.so.18()(64bit)
错误：软件包：perl-DBD-MySQL-4.023-6.el7.x86_64 (base)
          需要：libmysqlclient.so.18()(64bit)
 您可以尝试添加 --skip-broken 选项来解决该问题
** 发现 2 个已存在的 RPM 数据库问题， 'yum check' 输出如下：
2:postfix-2.10.1-7.el7.x86_64 有缺少的需求 libmysqlclient.so.18()(64bit)
2:postfix-2.10.1-7.el7.x86_64 有缺少的需求 libmysqlclient.so.18(libmysqlclient_18)(64bit)
[root@localhost mysql-5.7.26]# rpm -ivh mysql-community-libs-compat-5.7.18-1.el7.x86_64.rpm
错误：打开 mysql-community-libs-compat-5.7.18-1.el7.x86_64.rpm 失败： 没有那个文件或目录
[root@localhost mysql-5.7.26]# ll

安装perl-DBD-MySQL报错没有找到libmysqlclient.so.18()(64bit)，此时需要安装mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm包

[root@localhost mysql-5.7.26]# wget https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm
--2019-06-06 14:00:09--  https://dev.mysql.com/get/Downloads/MySQL-5.7/mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm
正在解析主机 dev.mysql.com (dev.mysql.com)... 137.254.60.11
正在连接 dev.mysql.com (dev.mysql.com)|137.254.60.11|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 302 Found
位置：https://cdn.mysql.com//Downloads/MySQL-5.7/mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm [跟随至新的 URL]
--2019-06-06 14:00:15--  https://cdn.mysql.com//Downloads/MySQL-5.7/mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm
正在解析主机 cdn.mysql.com (cdn.mysql.com)... 23.41.87.110
正在连接 cdn.mysql.com (cdn.mysql.com)|23.41.87.110|:443... 已连接。
已发出 HTTP 请求，正在等待回应... 200 OK
长度：2118444 (2.0M) [application/x-redhat-package-manager]
正在保存至: “mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm”

100%[===================================================================================>] 2,118,444   11.4KB/s 用时 2m 50s 

2019-06-06 14:03:09 (12.1 KB/s) - 已保存 “mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm” [2118444/2118444])

[root@localhost mysql-5.7.26]# rpm -ivh mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm
警告：mysql-community-libs-compat-5.7.26-1.el7.x86_64.rpm: 头V3 DSA/SHA1 Signature, 密钥 ID 5072e1f5: NOKEY
准备中...                          ################################# [100%]
正在升级/安装...
   1:mysql-community-libs-compat-5.7.2################################# [100%]

再次安装perl-DBD-MySQL

[root@localhost mysql-5.7.26]# yum install perl-DBD-MySQL
已加载插件：fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.huaweicloud.com
 * epel: mirrors.aliyun.com
 * extras: mirrors.aliyun.com
 * updates: mirrors.aliyun.com
正在解决依赖关系
--> 正在检查事务
---> 软件包 perl-DBD-MySQL.x86_64.0.4.023-6.el7 将被 安装
--> 解决依赖关系完成

依赖关系解决

=============================================================================================================================
 Package                           架构                      版本                              源                       大小
=============================================================================================================================
正在安装:
 perl-DBD-MySQL                    x86_64                    4.023-6.el7                       base                    140 k

事务概要
=============================================================================================================================
安装  1 软件包

总下载量：140 k
安装大小：323 k
Is this ok [y/d/N]: y
Downloading packages:
perl-DBD-MySQL-4.023-6.el7.x86_64.rpm                                                                 | 140 kB  00:00:00     
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
警告：RPM 数据库已被非 yum 程序修改。
  正在安装    : perl-DBD-MySQL-4.023-6.el7.x86_64                                                                        1/1 
  验证中      : perl-DBD-MySQL-4.023-6.el7.x86_64                                                                        1/1 

已安装:
  perl-DBD-MySQL.x86_64 0:4.023-6.el7                                                                                        

完毕！

再次测试repl

[root@localhost mysql-5.7.26]# masterha_check_repl --conf=/etc/masterha/app1.cnf 
Thu Jun  6 14:13:05 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Jun  6 14:13:05 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Thu Jun  6 14:13:05 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Thu Jun  6 14:13:05 2019 - [info] MHA::MasterMonitor version 0.58.
Thu Jun  6 14:13:06 2019 - [info] GTID failover mode = 1
Thu Jun  6 14:13:06 2019 - [info] Dead Servers:
Thu Jun  6 14:13:06 2019 - [info] Alive Servers:
Thu Jun  6 14:13:06 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Thu Jun  6 14:13:06 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Thu Jun  6 14:13:06 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Thu Jun  6 14:13:06 2019 - [info] Alive Slaves:
Thu Jun  6 14:13:06 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Thu Jun  6 14:13:06 2019 - [info]     GTID ON
Thu Jun  6 14:13:06 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Thu Jun  6 14:13:06 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Jun  6 14:13:06 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Thu Jun  6 14:13:06 2019 - [info]     GTID ON
Thu Jun  6 14:13:06 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Thu Jun  6 14:13:06 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Thu Jun  6 14:13:06 2019 - [info] Current Alive Master: 172.28.18.69(172.28.18.69:3306)
Thu Jun  6 14:13:06 2019 - [info] Checking slave configurations..
Thu Jun  6 14:13:06 2019 - [info]  read_only=1 is not set on slave 172.28.18.71(172.28.18.71:3306).
Thu Jun  6 14:13:06 2019 - [info]  read_only=1 is not set on slave 172.28.18.78(172.28.18.78:3306).
Thu Jun  6 14:13:06 2019 - [info] Checking replication filtering settings..
Thu Jun  6 14:13:06 2019 - [info]  binlog_do_db= , binlog_ignore_db= 
Thu Jun  6 14:13:06 2019 - [info]  Replication filtering check ok.
Thu Jun  6 14:13:06 2019 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Thu Jun  6 14:13:06 2019 - [info] Checking SSH publickey authentication settings on the current master..
Thu Jun  6 14:13:11 2019 - [warning] HealthCheck: Got timeout on checking SSH connection to 172.28.18.69! at /usr/local/share/perl5/MHA/HealthCheck.pm line 343.
Thu Jun  6 14:13:11 2019 - [info] 
172.28.18.69(172.28.18.69:3306) (current master)
 +--172.28.18.71(172.28.18.71:3306)
 +--172.28.18.78(172.28.18.78:3306)

Thu Jun  6 14:13:11 2019 - [info] Checking replication health on 172.28.18.71..
Thu Jun  6 14:13:11 2019 - [info]  ok.
Thu Jun  6 14:13:11 2019 - [info] Checking replication health on 172.28.18.78..
Thu Jun  6 14:13:11 2019 - [info]  ok.
Thu Jun  6 14:13:11 2019 - [warning] master_ip_failover_script is not defined.
Thu Jun  6 14:13:11 2019 - [warning] shutdown_script is not defined.
Thu Jun  6 14:13:11 2019 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

测试成功，信息显示：

Alive Slaves: 172.28.18.78 172.28.18.71 ---- 活动从库为172.28.18.78，

GTID ON--GTID复制模式开启

Replicating from 172.28.18.69 ----从172.28.18.69主库复制

Current Alive Master: 172.28.18.69(172.28.18.69:3306) --当前活动主库为172.28.18.69

九、后台启动MHA

[root@localhost bin]# masterha_manager --conf=/etc/masterha/app1.cnf &
[1] 12822
[root@localhost bin]# Thu Jun  6 10:25:43 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Thu Jun  6 10:25:43 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Thu Jun  6 10:25:43 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
^C
[root@localhost bin]#

查看进程

[root@localhost ~]# ps -ef|grep masterha
root     12822 10037  2 10:25 pts/3    00:00:00 perl /usr/local/bin/masterha_manager --conf=/etc/masterha/app1.cnf
root     12863 31965  0 10:25 pts/2    00:00:00 grep --color=auto masterha

十、查看MHA状态

[root@localhost bin]# masterha_check_status --conf=/etc/masterha/app1.cnf 
app1 (pid:12822) is running(0:PING_OK), master:172.28.18.69

十一、停止MHA

[root@localhost bin]# masterha_stop --conf=/etc/masterha/app1.cnf 
Stopped app1 successfully.
[1]+  退出 1                masterha_manager --conf=/etc/masterha/app1.cnf

十二、编写VIP切换脚本

[root@localhost /]# mkdir /etc/masterha/scripts
[root@localhost /]# cd /etc/masterha/scripts/[root@localhost scripts]# vim master_ip_failover

#!/usr/bin/env perl
use strict;
use warnings FATAL => 'all';

use Getopt::Long;

my (
    $command,          $ssh_user,        $orig_master_host, $orig_master_ip,
    $orig_master_port, $new_master_host, $new_master_ip,    $new_master_port
);

my $vip = '172.28.18.70/24';  # Virtual IP
my $key = "1";
my $int = "em1";
my $ssh_start_vip = "/user/sbin/ifconfig $int:$key $vip";
my $ssh_stop_vip = "/user/sbin/ifconfig $int:$key down";
$ssh_user = "root";
GetOptions(
    'command=s'          => \$command,
    'ssh_user=s'         => \$ssh_user,
    'orig_master_host=s' => \$orig_master_host,
    'orig_master_ip=s'   => \$orig_master_ip,
    'orig_master_port=i' => \$orig_master_port,
    'new_master_host=s'  => \$new_master_host,
    'new_master_ip=s'    => \$new_master_ip,
    'new_master_port=i'  => \$new_master_port,
);

exit &main();
sub main {

    print "\n\nIN SCRIPT TEST====$ssh_stop_vip==$ssh_start_vip===\n\n";

    if ( $command eq "stop" || $command eq "stopssh" ) {

        # $orig_master_host, $orig_master_ip, $orig_master_port are passed.
        # If you manage master ip address at global catalog database,
        # invalidate orig_master_ip here.
        my $exit_code = 1;
        eval {
            print "Disabling the VIP on old master: $orig_master_host \n";
            &stop_vip();
            $exit_code = 0;
        };
        if ($@) {
            warn "Got Error: $@\n";
            exit $exit_code;
        }
        exit $exit_code;
    }
    elsif ( $command eq "start" ) {

        # all arguments are passed.
        # If you manage master ip address at global catalog database,
        # activate new_master_ip here.
        # You can also grant write access (create user, set read_only=0, etc) here.
        my $exit_code = 10;
        eval {
            print "Enabling the VIP - $vip on the new master - $new_master_host \n";
            &start_vip();
            $exit_code = 0;
        };
        if ($@) {
            warn $@;
            exit $exit_code;
        }
        exit $exit_code;
    }
    elsif ( $command eq "status" ) {
        print "Checking the Status of the script.. OK \n";
        #`ssh $ssh_user\@cluster1 \" $ssh_start_vip \"`;
        &status();
        exit 0;
    }
    else {
        &usage();
        exit 1;
    }
}

# A simple system call that enable the VIP on the new master
sub start_vip() {
    `ssh $ssh_user\@$new_master_host \" $ssh_start_vip \"`;
    `ssh $ssh_user\@$new_master_host \" $arp_effect \"`;
#    `ssh $ssh_user\@$new_master_host \" $test \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
    `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
}

sub status() {
    print `ssh $ssh_user\@$orig_master_host \" ip add show $int \"`;
}

sub usage {
    print
    "Usage: master_ip_failover --command=start|stop|stopssh|status --orig_master_host=host --orig_master_ip=ip --orig_master_port=port --new_master_host=host --new_master_ip=ip --new_master_port=port\n";

}

十三、测试VIP切换脚本

1、首先使用start参数设置master服务器的VIP

[root@localhost scripts]# ./master_ip_failover --command=start  --new_master_host=172.28.18.71 


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Enabling the VIP - 172.28.18.70/24 on the new master - 172.28.18.71

查看VIP

[root@localhost scripts]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:2b:2b:5c:dc:15 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.71/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/24 brd 172.28.18.255 scope global em1:1
       valid_lft forever preferred_lft forever
    inet6 fe80::e0b8:7d61:e043:692/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: em2:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:17 brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:19 brd ff:ff:ff:ff:ff:ff
5: em4:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:1b brd ff:ff:ff:ff:ff:ff
6: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0

设置成功，

2、删除VIP

[root@localhost scripts]# ./master_ip_failover --command=stop  --orig_master_host=172.28.18.71 


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Disabling the VIP on old master: 172.28.18.71

查看结果

[root@localhost scripts]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:2b:2b:5c:dc:15 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.71/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet6 fe80::e0b8:7d61:e043:692/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: em2:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:17 brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:19 brd ff:ff:ff:ff:ff:ff
5: em4:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:1b brd ff:ff:ff:ff:ff:ff
6: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0

172.28.18.70的VIP已经被移除

3、查看目前VIP状态

[root@localhost scripts]# ./master_ip_failover --command=status --orig_master_host=172.28.18.71


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Checking the Status of the script.. OK 
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:2b:2b:5c:dc:15 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.71/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/24 brd 172.28.18.255 scope global em1:1
       valid_lft forever preferred_lft forever
    inet6 fe80::e0b8:7d61:e043:692/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

到此，整个环境搭建完毕，下一步测试故障转移

十四、测试故障转移

1、另开一个窗口，查看实时日志输出

[root@localhost ~]# tail -f /etc/masterha/manager.log

2、启动MHA

[root@localhost ~]# masterha_manager --conf=/etc/masterha/app1.cnf &
[1] 28459
[root@localhost ~]# Mon Jun 10 16:05:12 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon Jun 10 16:05:12 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Mon Jun 10 16:05:12 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..

3、查看日志

Mon Jun 10 16:05:12 2019 - [info] MHA::MasterMonitor version 0.58.
Mon Jun 10 16:05:14 2019 - [info] GTID failover mode = 1
Mon Jun 10 16:05:14 2019 - [info] Dead Servers:
Mon Jun 10 16:05:14 2019 - [info] Alive Servers:
Mon Jun 10 16:05:14 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Mon Jun 10 16:05:14 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Mon Jun 10 16:05:14 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Mon Jun 10 16:05:14 2019 - [info] Alive Slaves:
Mon Jun 10 16:05:14 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 16:05:14 2019 - [info]     GTID ON
Mon Jun 10 16:05:14 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 16:05:14 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 16:05:14 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 16:05:14 2019 - [info]     GTID ON
Mon Jun 10 16:05:14 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 16:05:14 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 16:05:14 2019 - [info] Current Alive Master: 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 16:05:14 2019 - [info] Checking slave configurations..
Mon Jun 10 16:05:14 2019 - [info]  read_only=1 is not set on slave 172.28.18.71(172.28.18.71:3306).
Mon Jun 10 16:05:14 2019 - [info] Checking replication filtering settings..
Mon Jun 10 16:05:14 2019 - [info]  binlog_do_db= , binlog_ignore_db= 
Mon Jun 10 16:05:14 2019 - [info]  Replication filtering check ok.
Mon Jun 10 16:05:14 2019 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Mon Jun 10 16:05:14 2019 - [info] Checking SSH publickey authentication settings on the current master..
Mon Jun 10 16:05:14 2019 - [info] HealthCheck: SSH to 172.28.18.69 is reachable.
Mon Jun 10 16:05:14 2019 - [info] 
172.28.18.69(172.28.18.69:3306) (current master)
 +--172.28.18.71(172.28.18.71:3306)
 +--172.28.18.78(172.28.18.78:3306)

Mon Jun 10 16:05:14 2019 - [info] Checking master_ip_failover_script status:
Mon Jun 10 16:05:14 2019 - [info]   /etc/masterha/scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=172.28.18.69 --orig_master_ip=172.28.18.69 --orig_master_port=3306  --orig_master_ssh_port=25601
Unknown option: orig_master_ssh_port


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Checking the Status of the script.. OK 
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:fe:b5:dc:2c:77 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.69/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/32 scope global em1
       valid_lft forever preferred_lft forever
    inet6 fe80::b3e8:e3b2:2242:a2ed/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
Mon Jun 10 16:05:14 2019 - [info]  OK.
Mon Jun 10 16:05:14 2019 - [warning] shutdown_script is not defined.
Mon Jun 10 16:05:14 2019 - [info] Set master ping interval 1 seconds.
Mon Jun 10 16:05:14 2019 - [info] Set secondary check script: masterha_secondary_check -s 172.28.18.71 -s 172.28.18.69 -s 172.28.18.78
Mon Jun 10 16:05:14 2019 - [info] Starting ping health check on 172.28.18.69(172.28.18.69:3306)..
Mon Jun 10 16:05:14 2019 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

日志中可以看出

172.28.18.69(172.28.18.69:3306) (current master)
 +--172.28.18.71(172.28.18.71:3306)
 +--172.28.18.78(172.28.18.78:3306)
172.28.18.69为主库， 172.28.18.71  ，172.28.18.78为从库
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:fe:b5:dc:2c:77 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.69/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/32 scope global em1
       valid_lft forever preferred_lft forever
    inet6 fe80::b3e8:e3b2:2242:a2ed/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever172.28.18.69上已经设置了172.28.18.70的VIP

4、将172.28.18.69服务器主库mysqld关掉，模拟故障

[root@server-1 ~]# killall mysqld
[root@server-1 ~]# ps -ef|grep mysqld
root      8188 29237  0 17:05 pts/0    00:00:00 grep --color=auto mysqld

5、观察172.28.18.71上的manager.log日志

Mon Jun 10 17:26:52 2019 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Mon Jun 10 17:26:52 2019 - [info] Executing secondary network check script: masterha_secondary_check -s 172.28.18.71 -s 172.28.18.69 -s 172.28.18.78  --user=root  --master_host=172.28.18.69  --master_ip=172.28.18.69  --master_port=3306 --master_user=root --master_password=Zaq1xsw@ --ping_type=SELECT
Mon Jun 10 17:26:52 2019 - [info] Executing SSH check script: exit 0
Mon Jun 10 17:26:52 2019 - [info] HealthCheck: SSH to 172.28.18.69 is reachable.
Monitoring server 172.28.18.71 is reachable, Master is not reachable from 172.28.18.71. OK.
Monitoring server 172.28.18.69 is reachable, Master is not reachable from 172.28.18.69. OK.
Mon Jun 10 17:26:53 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Mon Jun 10 17:26:53 2019 - [warning] Connection failed 2 time(s)..
Monitoring server 172.28.18.78 is reachable, Master is not reachable from 172.28.18.78. OK.
Mon Jun 10 17:26:53 2019 - [info] Master is not reachable from all other monitoring servers. Failover should start.
Mon Jun 10 17:26:54 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Mon Jun 10 17:26:54 2019 - [warning] Connection failed 3 time(s)..
Mon Jun 10 17:26:55 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Mon Jun 10 17:26:55 2019 - [warning] Connection failed 4 time(s)..
Mon Jun 10 17:26:55 2019 - [warning] Master is not reachable from health checker!
Mon Jun 10 17:26:55 2019 - [warning] Master 172.28.18.69(172.28.18.69:3306) is not reachable!
Mon Jun 10 17:26:55 2019 - [warning] SSH is reachable.
Mon Jun 10 17:26:55 2019 - [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..
Mon Jun 10 17:26:55 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Mon Jun 10 17:26:55 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Mon Jun 10 17:26:55 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Mon Jun 10 17:26:56 2019 - [info] GTID failover mode = 1
Mon Jun 10 17:26:56 2019 - [info] Dead Servers:
Mon Jun 10 17:26:56 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:56 2019 - [info] Alive Servers:
Mon Jun 10 17:26:56 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Mon Jun 10 17:26:56 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Mon Jun 10 17:26:56 2019 - [info] Alive Slaves:
Mon Jun 10 17:26:56 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 17:26:56 2019 - [info]     GTID ON
Mon Jun 10 17:26:56 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:56 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 17:26:56 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 17:26:56 2019 - [info]     GTID ON
Mon Jun 10 17:26:56 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:56 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 17:26:56 2019 - [info] Checking slave configurations..
Mon Jun 10 17:26:56 2019 - [info]  read_only=1 is not set on slave 172.28.18.71(172.28.18.71:3306).
Mon Jun 10 17:26:56 2019 - [info] Checking replication filtering settings..
Mon Jun 10 17:26:56 2019 - [info]  Replication filtering check ok.
Mon Jun 10 17:26:56 2019 - [info] Master is down!
Mon Jun 10 17:26:56 2019 - [info] Terminating monitoring script.
Mon Jun 10 17:26:56 2019 - [info] Got exit code 20 (Master dead).
Mon Jun 10 17:26:56 2019 - [info] MHA::MasterFailover version 0.58.
Mon Jun 10 17:26:56 2019 - [info] Starting master failover.
Mon Jun 10 17:26:56 2019 - [info] 
Mon Jun 10 17:26:56 2019 - [info] * Phase 1: Configuration Check Phase..
Mon Jun 10 17:26:56 2019 - [info] 
Mon Jun 10 17:26:57 2019 - [info] GTID failover mode = 1
Mon Jun 10 17:26:57 2019 - [info] Dead Servers:
Mon Jun 10 17:26:57 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:57 2019 - [info] Checking master reachability via MySQL(double check)...
Mon Jun 10 17:26:57 2019 - [info]  ok.
Mon Jun 10 17:26:57 2019 - [info] Alive Servers:
Mon Jun 10 17:26:57 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Mon Jun 10 17:26:57 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Mon Jun 10 17:26:57 2019 - [info] Alive Slaves:
Mon Jun 10 17:26:57 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 17:26:57 2019 - [info]     GTID ON
Mon Jun 10 17:26:57 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:57 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 17:26:57 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Mon Jun 10 17:26:57 2019 - [info]     GTID ON
Mon Jun 10 17:26:57 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Mon Jun 10 17:26:57 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Mon Jun 10 17:26:57 2019 - [error][/usr/local/share/perl5/MHA/MasterFailover.pm, ln310] Last failover was done at 2019/06/10 14:15:44. Current time is too early to do failover again. If you want to do failover, manually remove /etc/masterha//app1.failover.complete and run this script again.
Mon Jun 10 17:26:57 2019 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR:  at /usr/local/bin/masterha_manager line 65.

 报错：Current time is too early to do failover again，manually remove /etc/masterha/app1.failover.complete and run this script again
提示删除/etc/masterha//app1.failover.complete这个文件

[root@localhost scripts]# rm -rf /etc/masterha/app1.failover.complete
[root@localhost scripts]#

再次启动MHA,再次模拟172.28.18.69主库mysql故障

[root@server-1 ~]# mysqladmin -uroot -p -S /home/mysql-5.7.26/run/mysql.sock shutdown
Enter password: 
2019-06-11T01:49:32.127585Z mysqld_safe mysqld from pid file /home/mysql-5.7.26/run/mysqld.pid ended
[1]+  完成                  mysqld_safe --defaults-file=/etc/my.cnf --user=mysql

查看172.28.18.71上的manager.log日志

Tue Jun 11 09:49:22 2019 - [warning] Got error on MySQL select ping: 2013 (Lost connection to MySQL server during query)
Tue Jun 11 09:49:22 2019 - [info] Executing secondary network check script: masterha_secondary_check -s 172.28.18.71 -s 172.28.18.69 -s 172.28.18.78  --user=root  --master_host=172.28.18.69  --master_ip=172.28.18.69  --master_port=3306 --master_user=root --master_password=Zaq1xsw@ --ping_type=SELECT
Tue Jun 11 09:49:22 2019 - [info] Executing SSH check script: exit 0
Tue Jun 11 09:49:23 2019 - [info] HealthCheck: SSH to 172.28.18.69 is reachable.
Tue Jun 11 09:49:23 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Tue Jun 11 09:49:23 2019 - [warning] Connection failed 2 time(s)..
Monitoring server 172.28.18.71 is reachable, Master is not reachable from 172.28.18.71. OK.
Monitoring server 172.28.18.69 is reachable, Master is not reachable from 172.28.18.69. OK.
Tue Jun 11 09:49:24 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Tue Jun 11 09:49:24 2019 - [warning] Connection failed 3 time(s)..
Monitoring server 172.28.18.78 is reachable, Master is not reachable from 172.28.18.78. OK.
Tue Jun 11 09:49:24 2019 - [info] Master is not reachable from all other monitoring servers. Failover should start.
Tue Jun 11 09:49:25 2019 - [warning] Got error on MySQL connect: 2003 (Can't connect to MySQL server on '172.28.18.69' (111))
Tue Jun 11 09:49:25 2019 - [warning] Connection failed 4 time(s)..
Tue Jun 11 09:49:25 2019 - [warning] Master is not reachable from health checker!
Tue Jun 11 09:49:25 2019 - [warning] Master 172.28.18.69(172.28.18.69:3306) is not reachable!
Tue Jun 11 09:49:25 2019 - [warning] SSH is reachable.
Tue Jun 11 09:49:25 2019 - [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..
Tue Jun 11 09:49:25 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jun 11 09:49:25 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Jun 11 09:49:25 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Tue Jun 11 09:49:26 2019 - [info] GTID failover mode = 1
Tue Jun 11 09:49:26 2019 - [info] Dead Servers:
Tue Jun 11 09:49:26 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:26 2019 - [info] Alive Servers:
Tue Jun 11 09:49:26 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Tue Jun 11 09:49:26 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Tue Jun 11 09:49:26 2019 - [info] Alive Slaves:
Tue Jun 11 09:49:26 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:26 2019 - [info]     GTID ON
Tue Jun 11 09:49:26 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:26 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:26 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:26 2019 - [info]     GTID ON
Tue Jun 11 09:49:26 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:26 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:26 2019 - [info] Checking slave configurations..
Tue Jun 11 09:49:26 2019 - [info]  read_only=1 is not set on slave 172.28.18.71(172.28.18.71:3306).
Tue Jun 11 09:49:26 2019 - [info] Checking replication filtering settings..
Tue Jun 11 09:49:26 2019 - [info]  Replication filtering check ok.
Tue Jun 11 09:49:26 2019 - [info] Master is down!
Tue Jun 11 09:49:26 2019 - [info] Terminating monitoring script.
Tue Jun 11 09:49:26 2019 - [info] Got exit code 20 (Master dead).
Tue Jun 11 09:49:26 2019 - [info] MHA::MasterFailover version 0.58.
Tue Jun 11 09:49:26 2019 - [info] Starting master failover.
Tue Jun 11 09:49:26 2019 - [info] 
Tue Jun 11 09:49:26 2019 - [info] * Phase 1: Configuration Check Phase..
Tue Jun 11 09:49:26 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] GTID failover mode = 1
Tue Jun 11 09:49:28 2019 - [info] Dead Servers:
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info] Checking master reachability via MySQL(double check)...
Tue Jun 11 09:49:28 2019 - [info]  ok.
Tue Jun 11 09:49:28 2019 - [info] Alive Servers:
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Tue Jun 11 09:49:28 2019 - [info] Alive Slaves:
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info] Starting GTID based failover.
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] ** Phase 1: Configuration Check Phase completed.
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 2: Dead Master Shutdown Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] Forcing shutdown so that applications never connect to the current master..
Tue Jun 11 09:49:28 2019 - [info] Executing master IP deactivation script:
Tue Jun 11 09:49:28 2019 - [info]   /etc/masterha/scripts/master_ip_failover --orig_master_host=172.28.18.69 --orig_master_ip=172.28.18.69 --orig_master_port=3306 --command=stopssh --ssh_user=root   --orig_master_ssh_port=25601
Unknown option: orig_master_ssh_port


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Disabling the VIP on old master: 172.28.18.69 
Tue Jun 11 09:49:28 2019 - [info]  done.
Tue Jun 11 09:49:28 2019 - [warning] shutdown_script is not set. Skipping explicit shutting down of the dead master.
Tue Jun 11 09:49:28 2019 - [info] * Phase 2: Dead Master Shutdown Phase completed.
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 3: Master Recovery Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 3.1: Getting Latest Slaves Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] The latest binary log file/position on all slaves is master.000006:194
Tue Jun 11 09:49:28 2019 - [info] Latest slaves (Slaves that received relay log files to the latest):
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info] The oldest binary log file/position on all slaves is master.000006:194
Tue Jun 11 09:49:28 2019 - [info] Oldest slaves:
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 3.3: Determining New Master Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] Searching new master from slaves..
Tue Jun 11 09:49:28 2019 - [info]  Candidate masters from the configuration file:
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.71(172.28.18.71:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 09:49:28 2019 - [info]     GTID ON
Tue Jun 11 09:49:28 2019 - [info]     Replicating from 172.28.18.69(172.28.18.69:3306)
Tue Jun 11 09:49:28 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 09:49:28 2019 - [info]  Non-candidate masters:
Tue Jun 11 09:49:28 2019 - [info]  Searching from candidate_master slaves which have received the latest relay log events..
Tue Jun 11 09:49:28 2019 - [info] New master is 172.28.18.71(172.28.18.71:3306)
Tue Jun 11 09:49:28 2019 - [info] Starting master failover..
Tue Jun 11 09:49:28 2019 - [info] 
From:
172.28.18.69(172.28.18.69:3306) (current master)
 +--172.28.18.71(172.28.18.71:3306)
 +--172.28.18.78(172.28.18.78:3306)

To:
172.28.18.71(172.28.18.71:3306) (new master)
 +--172.28.18.78(172.28.18.78:3306)
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 3.3: New Master Recovery Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info]  Waiting all logs to be applied.. 
Tue Jun 11 09:49:28 2019 - [info]   done.
Tue Jun 11 09:49:28 2019 - [info] Getting new master's binlog name and position..
Tue Jun 11 09:49:28 2019 - [info]  slave-71.000005:194
Tue Jun 11 09:49:28 2019 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='172.28.18.71', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Tue Jun 11 09:49:28 2019 - [info] Master Recovery succeeded. File:Pos:Exec_Gtid_Set: slave-71.000005, 194, d24d8a53-880d-11e9-b1f3-842b2b5cdc15:1-6,
ee3e292b-866b-11e9-9df8-14feb5dc2c77:1-15
Tue Jun 11 09:49:28 2019 - [info] Executing master IP activate script:
Tue Jun 11 09:49:28 2019 - [info]   /etc/masterha/scripts/master_ip_failover --command=start --ssh_user=root --orig_master_host=172.28.18.69 --orig_master_ip=172.28.18.69 --orig_master_port=3306 --new_master_host=172.28.18.71 --new_master_ip=172.28.18.71 --new_master_port=3306 --new_master_user='root'  --orig_master_ssh_port=25601  --new_master_ssh_port=25601 --new_master_password=xxx
Unknown option: new_master_user
Unknown option: orig_master_ssh_port
Unknown option: new_master_ssh_port
Unknown option: new_master_password


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Enabling the VIP - 172.28.18.70/24 on the new master - 172.28.18.71 
Tue Jun 11 09:49:28 2019 - [info]  OK.
Tue Jun 11 09:49:28 2019 - [info] ** Finished master recovery successfully.
Tue Jun 11 09:49:28 2019 - [info] * Phase 3: Master Recovery Phase completed.
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 4: Slaves Recovery Phase..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] * Phase 4.1: Starting Slaves in parallel..
Tue Jun 11 09:49:28 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info] -- Slave recovery on host 172.28.18.78(172.28.18.78:3306) started, pid: 20990. Check tmp log /etc/masterha//172.28.18.78_3306_20190611094926.log if it takes time..
Tue Jun 11 09:49:35 2019 - [info] 
Tue Jun 11 09:49:35 2019 - [info] Log messages from 172.28.18.78 ...
Tue Jun 11 09:49:35 2019 - [info] 
Tue Jun 11 09:49:28 2019 - [info]  Resetting slave 172.28.18.78(172.28.18.78:3306) and starting replication from the new master 172.28.18.71(172.28.18.71:3306)..
Tue Jun 11 09:49:29 2019 - [info]  Executed CHANGE MASTER.
Tue Jun 11 09:49:35 2019 - [info]  Slave started.
Tue Jun 11 09:49:35 2019 - [info]  gtid_wait(d24d8a53-880d-11e9-b1f3-842b2b5cdc15:1-6,
ee3e292b-866b-11e9-9df8-14feb5dc2c77:1-15) completed on 172.28.18.78(172.28.18.78:3306). Executed 0 events.
Tue Jun 11 09:49:35 2019 - [info] End of log messages from 172.28.18.78.
Tue Jun 11 09:49:35 2019 - [info] -- Slave on host 172.28.18.78(172.28.18.78:3306) started.
Tue Jun 11 09:49:35 2019 - [info] All new slave servers recovered successfully.
Tue Jun 11 09:49:35 2019 - [info] 
Tue Jun 11 09:49:35 2019 - [info] * Phase 5: New master cleanup phase..
Tue Jun 11 09:49:35 2019 - [info] 
Tue Jun 11 09:49:35 2019 - [info] Resetting slave info on the new master..
Tue Jun 11 09:49:35 2019 - [info]  172.28.18.71: Resetting slave info succeeded.
Tue Jun 11 09:49:35 2019 - [info] Master failover to 172.28.18.71(172.28.18.71:3306) completed successfully.
Tue Jun 11 09:49:35 2019 - [info] 

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

app1: MySQL Master failover 172.28.18.69(172.28.18.69:3306) to 172.28.18.71(172.28.18.71:3306) succeeded

Master 172.28.18.69(172.28.18.69:3306) is down!

Check MHA Manager logs at localhost.localdomain:/etc/masterha/manager.log for details.

Started automated(non-interactive) failover.
Invalidated master IP address on 172.28.18.69(172.28.18.69:3306)
Selected 172.28.18.71(172.28.18.71:3306) as a new master.
172.28.18.71(172.28.18.71:3306): OK: Applying all logs succeeded.
172.28.18.71(172.28.18.71:3306): OK: Activated master IP address.
172.28.18.78(172.28.18.78:3306): OK: Slave started, replicating from 172.28.18.71(172.28.18.71:3306)
172.28.18.71(172.28.18.71:3306): Resetting slave info succeeded.
Master failover to 172.28.18.71(172.28.18.71:3306) completed successfully.

此时日志显示主库172.28.18.69故障，将172.28.18.71升级为主库，将VIP172.28.18.70漂移到172.28.18.71上

在172.28.18.71上查看IP

[root@localhost scripts]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:2b:2b:5c:dc:15 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.71/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/24 brd 172.28.18.255 scope global em1:1
       valid_lft forever preferred_lft forever
    inet6 fe80::e0b8:7d61:e043:692/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: em2:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:17 brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:19 brd ff:ff:ff:ff:ff:ff
5: em4:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 84:2b:2b:5c:dc:1b brd ff:ff:ff:ff:ff:ff
6: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
    link/ipip 0.0.0.0 brd 0.0.0.0

IP 已经漂移，在172.28.18.69上查看IP

[root@server-1 ~]# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 14:fe:b5:dc:2c:77 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.69/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet6 fe80::b3e8:e3b2:2242:a2ed/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: em2:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 14:fe:b5:dc:2c:79 brd ff:ff:ff:ff:ff:ff
4: em3:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 14:fe:b5:dc:2c:7b brd ff:ff:ff:ff:ff:ff
5: em4:  mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 14:fe:b5:dc:2c:7d brd ff:ff:ff:ff:ff:ff

VIP已经删除

十四、将故障服务器重新启动加入集群

1、首先启动故障服务器的MYSQL

[root@server-1 ~]# mysqld_safe --defaults-file=/etc/my.cnf --user=mysql &
[1] 32453
[root@server-1 ~]# 2019-06-11T02:09:02.264893Z mysqld_safe Logging to '/home/mysql-5.7.26/log/mysqld.log'.
2019-06-11T02:09:02.317370Z mysqld_safe Starting mysqld daemon with databases from /home/mysql-5.7.26/data

2、手动设置将172.28.18.69故障服务器的mysql作为新的主库172.28.18.71的从库

首先在172.28.18.71上的MHA日志 manager.log里查找CHANGE 语句

[root@localhost ~]# cat /etc/masterha/manager.log |grep CHANGE
Tue Jun 11 09:49:28 2019 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='172.28.18.71', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxx';
Tue Jun 11 09:49:29 2019 - [info]  Executed CHANGE MASTER.
[root@localhost ~]#

在172.28.18.69上的mysql里执行上面的语句使172.28.18.69成为172.28.18.71的从库

mysql> CHANGE MASTER TO MASTER_HOST='172.28.18.71', MASTER_PORT=3306, MASTER_AUTO_POSITION=1, MASTER_USER='repl', MASTER_PASSWORD='xxxxxxxx';
ERROR 2006 (HY000): MySQL server has gone away
No connection. Trying to reconnect...
Connection id:    2
Current database: test

Query OK, 0 rows affected, 2 warnings (0.16 sec)

mysql> start slave;
Query OK, 0 rows affected (0.01 sec)

查看从库状态

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 172.28.18.71
                  Master_User: repl
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: slave-71.000005
          Read_Master_Log_Pos: 194
               Relay_Log_File: server-1-relay-bin.000002
                Relay_Log_Pos: 365
        Relay_Master_Log_File: slave-71.000005
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
           Replicate_Do_Table: 
       Replicate_Ignore_Table: 
      Replicate_Wild_Do_Table: 
  Replicate_Wild_Ignore_Table: 
                   Last_Errno: 0
                   Last_Error: 
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 194
              Relay_Log_Space: 575
              Until_Condition: None
               Until_Log_File: 
                Until_Log_Pos: 0
           Master_SSL_Allowed: No
           Master_SSL_CA_File: 
           Master_SSL_CA_Path: 
              Master_SSL_Cert: 
            Master_SSL_Cipher: 
               Master_SSL_Key: 
        Seconds_Behind_Master: 0
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error: 
               Last_SQL_Errno: 0
               Last_SQL_Error: 
  Replicate_Ignore_Server_Ids: 
             Master_Server_Id: 71
                  Master_UUID: d24d8a53-880d-11e9-b1f3-842b2b5cdc15
             Master_Info_File: /home/mysql-5.7.26/data/master.info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
      Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
           Master_Retry_Count: 86400
                  Master_Bind: 
      Last_IO_Error_Timestamp: 
     Last_SQL_Error_Timestamp: 
               Master_SSL_Crl: 
           Master_SSL_Crlpath: 
           Retrieved_Gtid_Set: 
            Executed_Gtid_Set: d24d8a53-880d-11e9-b1f3-842b2b5cdc15:1-6,
ee3e292b-866b-11e9-9df8-14feb5dc2c77:1-15
                Auto_Position: 1
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 
1 row in set (0.00 sec)

ERROR: 
No query specified

此时，已经成为172.28.18.71的从库了

3、将172.28.18.71上的MHA启动

因为MHA在做故障切换后，会自动退出，所以每次故障恢复后，需要重新启动MHA

[root@localhost ~]# masterha_manager --conf=/etc/masterha/app1.cnf &
[2] 22275
[1]   完成                  masterha_manager --conf=/etc/masterha/app1.cnf
[root@localhost ~]# Tue Jun 11 10:15:25 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Tue Jun 11 10:15:25 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Tue Jun 11 10:15:25 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..

查看MHA状态

[root@localhost ~]# masterha_check_status --conf=/etc/masterha/app1.cnf &
[3] 22318
[root@localhost ~]# app1 (pid:22275) is running(0:PING_OK), master:172.28.18.71

运行中，再查看manager.log日志

Tue Jun 11 10:15:25 2019 - [info] MHA::MasterMonitor version 0.58.
Tue Jun 11 10:15:30 2019 - [info] GTID failover mode = 1
Tue Jun 11 10:15:30 2019 - [info] Dead Servers:
Tue Jun 11 10:15:30 2019 - [info] Alive Servers:
Tue Jun 11 10:15:30 2019 - [info]   172.28.18.71(172.28.18.71:3306)
Tue Jun 11 10:15:30 2019 - [info]   172.28.18.69(172.28.18.69:3306)
Tue Jun 11 10:15:30 2019 - [info]   172.28.18.78(172.28.18.78:3306)
Tue Jun 11 10:15:30 2019 - [info] Alive Slaves:
Tue Jun 11 10:15:30 2019 - [info]   172.28.18.69(172.28.18.69:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 10:15:30 2019 - [info]     GTID ON
Tue Jun 11 10:15:30 2019 - [info]     Replicating from 172.28.18.71(172.28.18.71:3306)
Tue Jun 11 10:15:30 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 10:15:30 2019 - [info]   172.28.18.78(172.28.18.78:3306)  Version=5.7.26-log (oldest major version between slaves) log-bin:enabled
Tue Jun 11 10:15:30 2019 - [info]     GTID ON
Tue Jun 11 10:15:30 2019 - [info]     Replicating from 172.28.18.71(172.28.18.71:3306)
Tue Jun 11 10:15:30 2019 - [info]     Primary candidate for the new Master (candidate_master is set)
Tue Jun 11 10:15:30 2019 - [info] Current Alive Master: 172.28.18.71(172.28.18.71:3306)
Tue Jun 11 10:15:30 2019 - [info] Checking slave configurations..
Tue Jun 11 10:15:30 2019 - [info]  read_only=1 is not set on slave 172.28.18.69(172.28.18.69:3306).
Tue Jun 11 10:15:30 2019 - [info] Checking replication filtering settings..
Tue Jun 11 10:15:30 2019 - [info]  binlog_do_db= , binlog_ignore_db= 
Tue Jun 11 10:15:30 2019 - [info]  Replication filtering check ok.
Tue Jun 11 10:15:30 2019 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Tue Jun 11 10:15:30 2019 - [info] Checking SSH publickey authentication settings on the current master..
Tue Jun 11 10:15:31 2019 - [info] HealthCheck: SSH to 172.28.18.71 is reachable.
Tue Jun 11 10:15:31 2019 - [info] 
172.28.18.71(172.28.18.71:3306) (current master)
 +--172.28.18.69(172.28.18.69:3306)
 +--172.28.18.78(172.28.18.78:3306)

Tue Jun 11 10:15:31 2019 - [info] Checking master_ip_failover_script status:
Tue Jun 11 10:15:31 2019 - [info]   /etc/masterha/scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=172.28.18.71 --orig_master_ip=172.28.18.71 --orig_master_port=3306  --orig_master_ssh_port=25601
Unknown option: orig_master_ssh_port


IN SCRIPT TEST====/usr/sbin/ifconfig em1:1 down==/usr/sbin/ifconfig em1:1 172.28.18.70/24===

Checking the Status of the script.. OK 
2: em1:  mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 84:2b:2b:5c:dc:15 brd ff:ff:ff:ff:ff:ff
    inet 172.28.18.71/28 brd 172.28.18.79 scope global noprefixroute em1
       valid_lft forever preferred_lft forever
    inet 172.28.18.70/24 brd 172.28.18.255 scope global em1:1
       valid_lft forever preferred_lft forever
    inet6 fe80::e0b8:7d61:e043:692/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
Tue Jun 11 10:15:31 2019 - [info]  OK.
Tue Jun 11 10:15:31 2019 - [warning] shutdown_script is not defined.
Tue Jun 11 10:15:31 2019 - [info] Set master ping interval 1 seconds.
Tue Jun 11 10:15:31 2019 - [info] Set secondary check script: masterha_secondary_check -s 172.28.18.71 -s 172.28.18.69 -s 172.28.18.78
Tue Jun 11 10:15:31 2019 - [info] Starting ping health check on 172.28.18.71(172.28.18.71:3306)..
Tue Jun 11 10:15:31 2019 - [info] Ping(SELECT) succeeded, waiting until MySQL doesn't respond..

172.28.18.71(172.28.18.71:3306) (current master)
 +--172.28.18.69(172.28.18.69:3306)
 +--172.28.18.78(172.28.18.78:3306)
此时172.28.18.71为新的主库，172.28.18.69、172.28.18.78为从库

你可能感兴趣的:(linux下mysql5.7的MHA高可用架构搭建)

斤斤计较的婚姻到底有多难？白心之岂必有为
很多人私聊我会问到在哪个人群当中斤斤计较的人最多？我都会回答他，一般婚姻出现问题的斤斤计较的人士会非常多，以我多年经验，在婚姻落的一塌糊涂的人当中，斤斤计较的人数占比在20～30%以上，也就是说10个婚姻出现问题的斤斤计较的人有2-3个有多不减。在婚姻出问题当中，有大量的心理不平衡的、尖酸刻薄的怨妇。在婚姻中仅斤斤计较有两种类型：第一种是物质上的，另一种是精神上的。在物质与精神上抠门已经严重的影响
情绪觉察日记第37天露露_e800
今天是家庭关系规划师的第二阶最后一天，慧萍老师帮我做了个案，帮我处理了埋在心底好多年的一份恐惧，并给了我深深的力量！这几天出来学习，爸妈过来婆家帮我带小孩，妈妈出于爱帮我收拾东西，并跟我先生和婆婆产生矛盾，妈妈觉得他们没有照顾好我…。今晚回家见到妈妈，我很欣赏她并赞扬她，妈妈说今晚要跟我睡我说好，当我们俩躺在床上准备睡觉的时候，我握着妈妈的手对她说:妈妈这几天辛苦你了，你看你多利害把我们的家收拾得
芦花鞋一四许叶晗
又是在一个寒冷的夏日里，青铜和葵花决定今天一起去卖芦花鞋，奶奶亲手给他们做了一碗热乎乎的粥对他们说:“就靠你们两挣生活费了这碗粥赶紧趁热喝了吧！”于是青铜和葵花喝完了奶奶给她们做的粥，就准备去镇上卖卢花鞋，这回青铜和葵花穿着新的芦花鞋来到了镇上。青铜这回看到了很多人都在卖，用手势表达对葵花说:“这回有好多人在抢我们生意呢！我们必须得吆喝起来。”葵花点了点头。可是谁知他们也大声的叫，卖芦花喽！卖芦花
QQ群采集助手，精准引流必备神器 2401_87347160 其他经验分享
功能概述微信群查找与筛选工具是一款专为微信用户设计的辅助工具，它通过关键词搜索功能，帮助用户快速找到相关的微信群，并提供筛选是否需要验证的群组的功能。主要功能关键词搜索：用户可以输入关键词，工具将自动查找包含该关键词的微信群。筛选功能：工具提供筛选机制，用户可以选择是否只显示需要验证或不需要验证的群组。精准引流：通过上述功能，用户可以更精准地找到目标群组，进行有效的引流操作。3.设备需求该工具可以
关于沟通这件事，项目经理不需要每次都面对面进行流程大师兄
很多项目经理都会遇到这样的问题，项目中由于事情太多，根本没有足够的时间去召开会议，那在这种情况下如何去有效地管理项目中的利益相关者？当然，不建议电子邮件也不需要开会的话，建议可以采取下面几种方式来形成有效的沟通，这几种方式可以帮助你努力的通过各种办法来保持和各方面的联系。项目经理首先要问自己几个问题，项目中哪些利益相关者是必须要进行沟通的？可以列出项目中所有的利益相关者清单，同时也整理出项目中哪些
机器学习与深度学习间关系与区别 ℒℴѵℯ心·动ꦿ໊ོ꫞ 人工智能学习深度学习 python
一、机器学习概述定义机器学习（MachineLearning,ML）是一种通过数据驱动的方法，利用统计学和计算算法来训练模型，使计算机能够从数据中学习并自动进行预测或决策。机器学习通过分析大量数据样本，识别其中的模式和规律，从而对新的数据进行判断。其核心在于通过训练过程，让模型不断优化和提升其预测准确性。主要类型1.监督学习（SupervisedLearning）监督学习是指在训练数据集中包含输入
铭刻于星（四十二）随风至
69夜晚，绍敏同学做完功课后，看了眼房外，没听到动静才敢从书包的夹层里拿出那个心形纸团。折痕压得很深，都有些旧了，想来是已经写好很久了。绍敏同学慢慢地、轻轻地捏开折叠处，待到全部拆开后，又反复抚平纸张，然后仔细地一字字默看。只是开头的三个字是第一次看到，让她心漏跳了几拍。“亲爱的绍敏：从四年级的时候，我就喜欢你了，但是我一直不敢说，怕影响你学习。六年级的时候听说有人跟你表白，你接受了，我很难过，但
底层逆袭到底有多难，不甘平凡的你准备好了吗？让吴起给你说说造命者说
底层逆袭到底有多难，不甘平凡的你准备好了吗？让吴起给你说说我叫吴起，生于公元前440年的战国初期，正是群雄并起、天下纷争不断的时候。后人说我是军事家、政治家、改革家，是兵家代表人物。评价我一生历仕鲁、魏、楚三国，通晓兵家、法家、儒家三家思想，在内政军事上都有极高的成就。周安王二十一年（公元前381年），因变法得罪守旧贵族，被人乱箭射死。我出生在卫国一个“家累万金”的富有家庭，从年轻时候起就不甘平凡
2020-01-25 晴岚85
郑海燕坚持分享590天2020.1.24在生活中只存在两个问题。一个问题是：你知道想要达成的目标是什么，但却不知道如何才能达成；另一个问题是：你不知道你的目标是什么。前一个是行动的问题，后一个是结果的问题。通过制定具体的下一步行动，可以解决不知道如何开始行动的问题。而通过去想象结果，对结果做预估，可以解决找不着目标的问题。对于所有吸引我们注意力，想要完成的任务，你可以先想象一下，预期的结果究竟是什
随笔 | 仙一般的灵气海思沧海
仙岛今天，我看了你全部，似乎已经进入你的世界我不知道，这是否是梦幻，还是你仙一般的灵气吸引了我也许每一个人都要有一份属于自己的追求，这样才能够符合人生的梦想，生活才能够充满着阳光与快乐我不知道，我为什么会这样的感叹，是在感叹自己的人生，还是感叹自己一直没有孜孜不倦的追求只感觉虚度了光阴，每天活在自己的梦中，活在一个不真实的世界是在逃避自己，还是在逃避周围的一切有时候我嘲笑自己，嘲笑自己如此的虚无，
想家爆米花机
也许不同于大家对家乡的思念，我对家乡甚至是疯狂的不舍。还未踏出车站就感觉到幸福，我享受这里的夕阳、这里的浓烈柴火味、这里每一口家常菜。我是宅女，我贪恋家的安逸。刚刚踏出大学校门，初出茅庐，无法适应每年只能国庆和春节回家。我焦虑、失眠、无端发脾气，是无法适应工作的节奏，是无法接受我将一步步离开家乡的事实。我不想承认自己胸无大志，选择再次踏上征程。图片发自App
【iOS】MVC设计模式 Magnetic_h ios mvc 设计模式 objective-c 学习 ui
MVC前言如何设计一个程序的结构，这是一门专门的学问，叫做"架构模式"（architecturalpattern），属于编程的方法论。MVC模式就是架构模式的一种。它是Apple官方推荐的App开发架构，也是一般开发者最先遇到、最经典的架构。MVC各层controller层Controller/ViewController/VC（控制器）负责协调Model和View，处理大部分逻辑它将数据从Mod
OC语言多界面传值五大方式 Magnetic_h ios ui 学习 objective-c 开发语言
前言在完成暑假仿写项目时，遇到了许多需要用到多界面传值的地方，这篇博客来总结一下比较常用的五种多界面传值的方式。属性传值属性传值一般用前一个界面向后一个界面传值，简单地说就是通过访问后一个视图控制器的属性来为它赋值，通过这个属性来做到从前一个界面向后一个界面传值。首先在后一个界面中定义属性@interfaceBViewController:UIViewController@propertyNSSt
一百九十四章. 自相矛盾巨木擎天
唉！就这么一夜，林子感觉就像过了很多天似的，先是回了阳间家里，遇到了那么多不可思议的事情儿。特别是小伙伴们，第二次与自己见面时，僵硬的表情和恐怖的气氛，让自己如坐针毡，打从心眼里难受！还有东子，他现在还好吗？有没有被人欺负？护城河里的小鱼小虾们，还都在吗？水不会真的干枯了吧？那对相亲相爱漂亮的太平鸟儿，还好吧！春天了，到了做窝、下蛋、喂养小鸟宝宝的时候了，希望它们都能够平安啊！虽然没有看见家人，也
UI学习——cell的复用和自定义cell Magnetic_h ui 学习
目录cell的复用手动（非注册）自动（注册）自定义cellcell的复用在iOS开发中，单元格复用是一种提高表格（UITableView）和集合视图（UICollectionView）滚动性能的技术。当一个UITableViewCell或UICollectionViewCell首次需要显示时，如果没有可复用的单元格，则视图会创建一个新的单元格。一旦这个单元格滚动出屏幕，它就不会被销毁。相反，它被添
element实现动态路由+面包屑软件技术NINI vue案例 vue.js 前端
el-breadcrumb是ElementUI组件库中的一个面包屑导航组件，它用于显示当前页面的路径，帮助用户快速理解和导航到应用的各个部分。在Vue.js项目中，如果你已经安装了ElementUI，就可以很方便地使用el-breadcrumb组件。以下是一个基本的使用示例：安装ElementUI（如果你还没有安装的话）:你可以通过npm或yarn来安装ElementUI。bash复制代码npmi
10月|愿你的青春不负梦想-读书笔记-01 Tracy的小书斋
本书的作者是俞敏洪，大家都很熟悉他了吧。俞敏洪老师是我行业的领头羊吧，也是我事业上的偶像。本日摘录他书中第一章中的金句：『一个人如果什么目标都没有，就会浑浑噩噩，感觉生命中缺少能量。能给我们能量的，是对未来的期待。第一件事，我始终为了进步而努力。与其追寻全世界的骏马，不如种植丰美的草原，到时骏马自然会来。第二件事，我始终有阶段性的目标。什么东西能给我能量？答案是对未来的期待。』读到这里的时候，我便
C语言宏函数南林yan C语言 c语言
一、什么是宏函数？通过宏定义的函数是宏函数。如下，编译器在预处理阶段会将Add(x,y)替换为((x)*(y))#defineAdd(x,y)((x)*(y))#defineAdd(x,y)((x)*(y))intmain(){inta=10;intb=20;intd=10;intc=Add(a+d,b)*2;cout<
地推话术，如何应对地推过程中家长的拒绝校师学
相信校长们在做地推的时候经常遇到这种情况：市场专员反馈家长不接单，咨询师反馈难以邀约这些家长上门，校区地推疲软，招生难。为什么？仅从地推层面分析，一方面因为家长受到的信息轰炸越来越多，对信息越来越“免疫”；而另一方面地推人员的专业能力和营销话术没有提高，无法应对家长的拒绝，对有意向的家长也不知如何跟进，眼睁睁看着家长走远；对于家长的疑问，更不知道如何有技巧地回答，机会白白流失。由于回答没技巧和专业
谢谢你们，爱你们！鹿游儿
昨天家人去泡温泉，二个孩子也带着去，出发前一晚，匆匆下班，赶回家和孩子一起收拾。饭后，我拿出笔和本子（上次去澳门时做手帐的本子）写下了1\2\3\4\5\6\7\8\9,让后让小壹去思考，带什么出发去旅游呢？她在对应的数字旁边画上了，泳衣、泳圈、肖恩、内衣内裤、tapuy、拖鞋……画完后，就让她自己对着这个本子，将要带的，一一带上，没想到这次带的书还是这本《便便工厂》(晚上姑婆发照片过来，妹妹累得
C语言如何定义宏函数？小九格物 c语言
在C语言中，宏函数是通过预处理器定义的，它在编译之前替换代码中的宏调用。宏函数可以模拟函数的行为，但它们不是真正的函数，因为它们在编译时不会进行类型检查，也不会分配存储空间。宏函数的定义通常使用#define指令，后面跟着宏的名称和参数列表，以及宏展开后的代码。宏函数的定义方式：1.基本宏函数：这是最简单的宏函数形式，它直接定义一个表达式。#defineSQUARE(x)((x)*(x))2.带参
微服务下功能权限与数据权限的设计与实现 nbsaas-boot 微服务 java 架构
在微服务架构下，系统的功能权限和数据权限控制显得尤为重要。随着系统规模的扩大和微服务数量的增加，如何保证不同用户和服务之间的访问权限准确、细粒度地控制，成为设计安全策略的关键。本文将讨论如何在微服务体系中设计和实现功能权限与数据权限控制。1.功能权限与数据权限的定义功能权限：指用户或系统角色对特定功能的访问权限。通常是某个用户角色能否执行某个操作，比如查看订单、创建订单、修改用户资料等。数据权限：
理解Gunicorn：Python WSGI服务器的基石范范0825 ipython linux 运维
理解Gunicorn：PythonWSGI服务器的基石介绍Gunicorn，全称GreenUnicorn，是一个为PythonWSGI（WebServerGatewayInterface）应用设计的高效、轻量级HTTP服务器。作为PythonWeb应用部署的常用工具，Gunicorn以其高性能和易用性著称。本文将介绍Gunicorn的基本概念、安装和配置，帮助初学者快速上手。1.什么是Gunico
小丽成长记（四十三）玲玲54321
小丽发现，即使她好不容易调整好自己的心态下一秒总会有不确定的伤脑筋的事出现，一个接一个的问题，人生就没有停下的时候，小问题不断出现。不过她今天看的书，她接受了人生就是不确定的，厉害的人就是不断创造确定性，在Ta的领域比别人多的确定性就能让自己脱颖而出，显示价值从而获得的比别人多的利益。正是这样的原因，因为从前修炼自己太少，使得她现在在人生道路上打怪起来困难重重，她似乎永远摆脱不了那种无力感，有种习
学点心理知识，呵护孩子健康静候花开_7090
昨天听了华中师范大学教育管理学系副教授张玲老师的《哪里才是学生心理健康的最后庇护所，超越教育与技术的思考》的讲座。今天又重新学习了一遍，收获匪浅。张玲博士也注意到了当今社会上的孩子由于心理问题导致的自残、自杀及伤害他人等恶性事件。她向我们普及了一个重要的命题，她说心理健康的一些基本命题，我们与我们通常的一些教育命题是不同的，她还举了几个例子，让我们明白我们原来以为的健康并非心理学上的健康。比如如果
2021年12月19日，春蕾教育集团团建活动感受——黄晓丹黄错错加油
感受:1.从陌生到熟悉的过程。游戏环节让我们在轻松的氛围中得到了锻炼，也增长了不少知识。2.游戏过程中，我们贡献的是个人力量，展现的是团队的力量。它磨合的往往不止是工作的熟悉，更是观念上契合度的贴近。3.这和工作是一样的道理。在各自的岗位上，每个人摆正自己的位置、各司其职充分发挥才能，并团结一致劲往一处使，才能实现最大的成功。新知:1.团队精神需要不断地创新。过去，人们把创新看作是冒风险，现在人们
Cell Insight | 单细胞测序技术又一新发现，可用于HIV-1和Mtb共感染个体诊断尐尐呅
结核病是艾滋病合并其他疾病中导致患者死亡的主要原因。其中结核病由结核分枝杆菌（Mycobacteriumtuberculosis,Mtb）感染引起，获得性免疫缺陷综合症（艾滋病）由人免疫缺陷病毒（Humanimmunodeficiencyvirustype1,HIV-1）感染引起。国家感染性疾病临床医学研究中心/深圳市第三人民医院张国良团队携手深圳华大生命科学研究院吴靓团队，共同研究得出单细胞测序
c++ 的iostream 和 c++的stdio的区别和联系黄卷青灯77 c++算法开发语言 iostream stdio
在C++中，iostream和C语言的stdio.h都是用于处理输入输出的库，但它们在设计、用法和功能上有许多不同。以下是两者的区别和联系：区别1.编程风格iostream（C++风格）：C++标准库中的输入输出流类库，支持面向对象的输入输出操作。典型用法是cin（输入）和cout（输出），使用>操作符来处理数据。更加类型安全，支持用户自定义类型的输入输出。#includeintmain(){in
瑶池防线谜影梦蝶
冥华虽然逃过了影梦的军队，但他是一个忠臣，他选择上报战况。败给影梦后成逃兵，高层亡尔还活着，七重天失守......随便一条，即可处死冥华。冥华自然是知道以仙界高层的习性此信一发自己必死无疑，但他还选择上报实情，因为责任。同样此信送到仙宫后，知道此事的人，大多数人都认定冥华要完了，所以上到仙界高层，下到扫大街的，包括冥华自己，全都准备好迎接冥华之死。如果仙界现在还属于两方之争的话，冥华必死无疑。然而
爬山后遗症璃绛
爬山，攀登，一步一步走向制高点，是一种挑战。成功抵达是一种无法言语的快乐，在山顶吹吹风，看看风景，这是从未有过的体验。然而，爬山一时爽，下山腿打颤，颠簸的路，一路向下走，腿部力量不够，走起来抖到不行，停不下来了！第二天必定腿疼，浑身酸痛，坐立难安！
ViewController添加button按钮解析。（翻译）张亚雄 c
<div class="it610-blog-content-contain" style="font-size: 14px"></div>// ViewController.m // Reservation software // // Created by 张亚雄 on 15/6/2.
mongoDB 简单的增删改查开窍的石头 mongodb
在上一篇文章中我们已经讲了mongodb怎么安装和数据库/表的创建。在这里我们讲mongoDB的数据库操作在mongo中对于不存在的表当你用db.表名他会自动统计下边用到的user是表明，db代表的是数据库添加(insert):
log4j配置 0624chenhong log4j
1) 新建java项目 2) 导入jar包，项目右击，properties—java build path—libraries—Add External jar，加入log4j.jar包。 3) 新建一个类com.hand.Log4jTest package com.hand; import org.apache.log4j.Logger; public class
多点触摸(图片缩放为例) 不懂事的小屁孩多点触摸
多点触摸的事件跟单点是大同小异的，上个图片缩放的代码，供大家参考一下 import android.app.Activity; import android.os.Bundle; import android.view.MotionEvent; import android.view.View; import android.view.View.OnTouchListener
有关浏览器窗口宽度高度几个值的解析换个号韩国红果果 JavaScript html
1 元素的 offsetWidth 包括border padding content 整体的宽度。 clientWidth 只包括内容区 padding 不包括border。 clientLeft = offsetWidth -clientWidth 即这个元素border的值 offsetLeft 若无已定位的包裹元素
数据库产品巡礼：IBM DB2概览蓝儿唯美 db2
IBM DB2是一个支持了NoSQL功能的关系数据库管理系统，其包含了对XML，图像存储和Java脚本对象表示（JSON）的支持。DB2可被各种类型的企业使用，它提供了一个数据平台，同时支持事务和分析操作，通过提供持续的数据流来保持事务工作流和分析操作的高效性。 DB2支持的操作系统 DB2可应用于以下三个主要的平台: 工作站，DB2可在Linus、Unix、Windo
java笔记5 a-john java
控制执行流程： 1，true和false 利用条件表达式的真或假来决定执行路径。例：（a==b）。它利用条件操作符“==”来判断a值是否等于b值，返回true或false。java不允许我们将一个数字作为布尔值使用，虽然这在C和C++里是允许的。如果想在布尔测试中使用一个非布尔值，那么首先必须用一个条件表达式将其转化成布尔值，例如if(a!=0)。 2，if-els
Web开发常用手册汇总 aijuans PHP
一门技术，如果没有好的参考手册指导,很难普及大众。这其实就是为什么很多技术，非常好，却得不到普遍运用的原因。正如我们学习一门技术，过程大概是这个样子： ①我们日常工作中，遇到了问题，困难。寻找解决方案，即寻找新的技术； ②为什么要学习这门技术？这门技术是不是很好的解决了我们遇到的难题，困惑。这个问题，非常重要，我们不是为了学习技术而学习技术，而是为了更好的处理我们遇到的问题，才需要学习新的
今天帮助人解决的一个sql问题 asialee sql
今天有个人问了一个问题，如下： type AD value A
意图对象传递数据百合不是茶 android 意图Intent Bundle对象数据的传递
学习意图将数据传递给目标活动; 初学者需要好好研究的 1,将下面的代码添加到main.xml中 <?xml version="1.0" encoding="utf-8"?> <LinearLayout xmlns:android="http:/
oracle查询锁表解锁语句 bijian1013 oracle object session kill
一.查询锁定的表如下语句，都可以查询锁定的表语句一： select a.sid, a.serial#, p.spid, c.object_name, b.session_id, b.oracle_username, b.os_user_name from v$process p, v$s
mac osx 10.10 下安装 mysql 5.6 二进制文件［tar.gz］征客丶 mysql osx
场景：在 mac osx 10.10 下安装 mysql 5.6 的二进制文件。环境：mac osx 10.10、mysql 5.6 的二进制文件步骤：[所有目录请从根“/”目录开始取，以免层级弄错导致找不到目录] 1、下载 mysql 5.6 的二进制文件，下载目录下面称之为 mysql5.6SourceDir；下载地址：http://dev.mysql.com/downl
分布式系统与框架 bit1129 分布式
RPC框架 Dubbo 什么是Dubbo Dubbo是一个分布式服务框架，致力于提供高性能和透明化的RPC远程服务调用方案，以及SOA服务治理方案。其核心部分包含: 远程通讯: 提供对多种基于长连接的NIO框架抽象封装，包括多种线程模型，序列化，以及“请求-响应”模式的信息交换方式。集群容错: 提供基于接
那些令人蛋痛的专业术语白糖_ spring Web SSO IOC
spring 【控制反转(IOC)/依赖注入(DI)】：由容器控制程序之间的关系，而非传统实现中，由程序代码直接操控。这也就是所谓“控制反转”的概念所在：控制权由应用代码中转到了外部容器，控制权的转移，是所谓反转。简单的说：对象的创建又容器(比如spring容器)来执行，程序里不直接new对象。 Web 【单点登录(SSO)】：SSO的定义是在多个应用系统中，用户
《给大忙人看的java8》摘抄 braveCS java8
函数式接口：只包含一个抽象方法的接口 lambda表达式：是一段可以传递的代码你最好将一个lambda表达式想象成一个函数，而不是一个对象，并记住它可以被转换为一个函数式接口。事实上，函数式接口的转换是你在Java中使用lambda表达式能做的唯一一件事。方法引用：又是要传递给其他代码的操作已经有实现的方法了，这时可以使
编程之美-计算字符串的相似度 bylijinnan java 算法编程之美
public class StringDistance { /** * 编程之美计算字符串的相似度 * 我们定义一套操作方法来把两个不相同的字符串变得相同，具体的操作方法为： * 1.修改一个字符（如把“a”替换为“b”）; * 2.增加一个字符（如把“abdd”变为“aebdd”）; * 3.删除一个字符（如把“travelling”变为“trav
上传、下载压缩图片 chengxuyuancsdn 下载
/** * * @param uploadImage --本地路径(tomacat路径) * @param serverDir --服务器路径 * @param imageType --文件或图片类型 * 此方法可以上传文件或图片.txt,.jpg,.gif等 */ public void upload(String uploadImage,Str
bellman-ford(贝尔曼-福特)算法 comsci 算法 F#
Bellman-Ford算法(根据发明者 Richard Bellman 和 Lester Ford 命名)是求解单源最短路径问题的一种算法。单源点的最短路径问题是指：给定一个加权有向图G和源点s，对于图G中的任意一点v，求从s到v的最短路径。有时候这种算法也被称为 Moore-Bellman-Ford 算法，因为 Edward F. Moore zu 也为这个算法的发展做出了贡献。与迪科
oracle ASM中ASM_POWER_LIMIT参数 daizj ASM oracle ASM_POWER_LIMIT 磁盘平衡
ASM_POWER_LIMIT 该初始化参数用于指定ASM例程平衡磁盘所用的最大权值，其数值范围为0~11，默认值为1。该初始化参数是动态参数，可以使用ALTER SESSION或ALTER SYSTEM命令进行修改。示例如下： SQL>ALTER SESSION SET Asm_power_limit=2;
高级排序:快速排序 dieslrae 快速排序
public void quickSort(int[] array){ this.quickSort(array, 0, array.length - 1); } public void quickSort(int[] array,int left,int right){ if(right - left <= 0
C语言学习六指针_何谓变量的地址一个指针变量到底占几个字节 dcj3sjt126com C语言
# include <stdio.h> int main(void) { /* 1、一个变量的地址只用第一个字节表示 2、虽然他只使用了第一个字节表示，但是他本身指针变量类型就可以确定出他指向的指针变量占几个字节了 3、他都只存了第一个字节地址，为什么只需要存一个字节的地址，却占了4个字节，虽然只有一个字节，但是这些字节比较多，所以编号就比较大，
phpize使用方法 dcj3sjt126com PHP
phpize是用来扩展php扩展模块的，通过phpize可以建立php的外挂模块,下面介绍一个它的使用方法,需要的朋友可以参考下安装（fastcgi模式）的时候，常常有这样一句命令：代码如下: /usr/local/webserver/php/bin/phpize 一、phpize是干嘛的？ phpize是什么？ phpize是用来扩展php扩展模块的，通过phpi
Java虚拟机学习 - 对象引用强度 shuizhaosi888 JAVA虚拟机
本文原文链接：http://blog.csdn.net/java2000_wl/article/details/8090276 转载请注明出处！无论是通过计数算法判断对象的引用数量，还是通过根搜索算法判断对象引用链是否可达，判定对象是否存活都与“引用”相关。引用主要分为：强引用(Strong Reference)、软引用(Soft Reference)、弱引用(Wea
.NET Framework 3.5 Service Pack 1（完整软件包）下载地址 happyqing .net 下载 framework
Microsoft .NET Framework 3.5 Service Pack 1（完整软件包） http://www.microsoft.com/zh-cn/download/details.aspx?id=25150 Microsoft .NET Framework 3.5 Service Pack 1 是一个累积更新，包含很多基于 .NET Framewo
JAVA定时器的使用 jingjing0907 java timer 线程定时器
1、在应用开发中，经常需要一些周期性的操作，比如每5分钟执行某一操作等。对于这样的操作最方便、高效的实现方式就是使用java.util.Timer工具类。 privatejava.util.Timer timer; timer = newTimer(true); timer.schedule( newjava.util.TimerTask() { public void run()
Webbench 流浪鱼 webbench
首页下载地址 http://home.tiscali.cz/~cz210552/webbench.html Webbench是知名的网站压力测试工具，它是由Lionbridge公司（http://www.lionbridge.com）开发。 Webbench能测试处在相同硬件上，不同服务的性能以及不同硬件上同一个服务的运行状况。webbench的标准测试可以向我们展示服务器的两项内容：每秒钟相
第11章动画效果（中） onestopweb 动画
index.html <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/
windows下制作bat启动脚本. sanyecao2314 java cmd 脚本 bat
java -classpath C:\dwjj\commons-dbcp.jar;C:\dwjj\commons-pool.jar;C:\dwjj\log4j-1.2.16.jar;C:\dwjj\poi-3.9-20121203.jar;C:\dwjj\sqljdbc4.jar;C:\dwjj\voucherimp.jar com.citsamex.core.startup.MainStart
Java进行RSA加解密的例子 tomcat_oracle java
加密是保证数据安全的手段之一。加密是将纯文本数据转换为难以理解的密文；解密是将密文转换回纯文本。　　数据的加解密属于密码学的范畴。通常，加密和解密都需要使用一些秘密信息，这些秘密信息叫做密钥，将纯文本转为密文或者转回的时候都要用到这些密钥。　　对称加密指的是发送者和接收者共用同一个密钥的加解密方法。　　非对称加密(又称公钥加密)指的是需要一个私有密钥一个公开密钥，两个不同的密钥的
Android_ViewStub 阿尔萨斯 ViewStub
public final class ViewStub extends View java.lang.Object android.view.View android.view.ViewStub 类摘要： ViewStub 是一个隐藏的，不占用内存空间的视图对象，它可以在运行时延迟加载布局资源文件。当 ViewSt