MySQL高可用之MHA

最新推荐文章于 2024-05-31 15:55:19 发布

现实如此呀

最新推荐文章于 2024-05-31 15:55:19 发布

阅读量261

点赞数

分类专栏： MySQL 文章标签：数据库 mysql MHA keepalived

本文链接：https://blog.csdn.net/weixin_47019016/article/details/114656180

版权

MySQL 专栏收录该内容

24 篇文章 4 订阅

订阅专栏

MHA环境部署

一、MHA相关简介
- 二、MHA前提环境部署
- - 三、配置MySQL半同步复制
  - - 四、安装部署mysql-mha
    - - 五、MHA Manager端常用操作
      - 六、配置VIP

一、MHA相关简介

1.MHA简介
MHA（Master High Availability）目前在MySQL高可用方面是一个相对成熟的解决方案，它由日本DeNA公司youshimaton（现就职于Facebook公司）开发，是一套优秀的作为MySQL高可用性环境下故障切换和主从提升的高可用软件。在MySQL故障切换过程中，MHA能做到在0~30秒之内自动完成数据库的故障切换操作，并且在进行故障切换的过程中，MHA能在最大程度上保证数据的一致性，以达到真正意义上的高可用。
MHA里有两个角色一个是MHA Node，另一个是MHA Manager。
MHA Manager可以单独部署在一台独立的机器上管理多个master-slave集群，也可以部署在一台slave节点上。MHA Node运行在每台MySQL服务器上，MHA Manager会定时探测集群中的master节点，当master出现故障时，它可以自动将最新数据的slave提升为新的master，然后将所有其他的slave重新指向新的master。整个故障转移过程对应用程序完全透明。
在这里插入图片描述
2.MySQL数据复制的分类
MHA自动故障切换过程中，MHA试图从宕机的主服务器上保存二进制日志，最大程度的保证数据的不丢失，但这并不总是可行的。例如，如果主服务器硬件故障或无法通过ssh访问，MHA没法保存二进制日志，只进行故障转移而丢失了最新的数据。使用MySQL的半同步复制，可以大大降低数据丢失的风险。MHA可以与半同步复制结合起来。如果只有一个slave已经收到了最新的二进制日志，MHA可以将最新的二进制日志应用于其他所有的slave服务器上，因此可以保证所有节点的数据一致性。
注意：从MySQL5.5开始，MySQL以插件的形式支持半同步复制。

(1)异步复制（Asynchronous replication）
MySQL默认的复制机制是异步，主库在执行完客户端提交的事务后会立即将结果返给给客户端，并不关心从库是否已经接收并处理。
这样就会有一个问题，主如果crash掉了，此时主上已经提交的事务可能并没有传到从上，如果此时强行将从提升为主，可能导致新主上的数据不完整。

(2)全同步复制（Fully synchronous replication）
指当主库执行完一个事务，所有的从库都执行了该事务才返回给客户端。
因为需要等待所有从库执行完该事务才能返回，所以全同步复制的性能必然会收到严重的影响。

(3)半同步复制（Semisynchronous replication）
介于异步复制和全同步复制之间，主库在执行完客户端提交的事务后不是立刻返回给客户端，而是等待至少一个从库接收到并写到relay log中才返回给客户端。
相对于异步复制，半同步复制提高了数据的安全性，同时它也造成了一定程度的延迟，这个延迟最少是一个TCP/IP往返的时间。所以，半同步复制最好在低延时的网络中使用。

总结：
默认情况下MySQL的复制是异步，Master上所有的更新操作写入Binlog后，并不确保所有的更新都被复制到Slave之上。异步操作虽然效率高，但是在Master/Slave出现问题时，存在很高数据不同步的风险，甚至可能丢失数据。
MySQL5.5引入半同步复制功能的目的是为了保证在master出问题时，至少有一台Slave的数据是完整的。在超时的情况下也可以临时转入异步复制，保障业务的正常使用，直到一台salve追赶上之后，继续切换到半同步模式。
3.MHA工作原理
相较于其它HA软件，MHA的目的在于维持MySQL Replication中Master库的高可用性，其最大特点是可以修复多个Slave之间的差异日志，最终使所有Slave保持数据一致，然后从中选择一个充当新的Master，并将其它Slave指向它。

(1)从宕机崩溃的master保存二进制日志事件(binlog events)。

(2)识别含有最新更新的slave。

(3)应用差异的中继日志(relay log)到其它slave。

(4)应用从master保存的二进制日志事件(binlog events)。

(5)提升一个slave为新master。

(6)使其它的slave连接新的master进行复制。

二、MHA前提环境部署

目前MHA主要支持一主多从的架构，要搭建MHA，要求一个复制集群中必须最少有三台数据库服务器，一主二从，即一台充当master，一台充当备用master，另外一台充当从库。
1.环境准备

角色	IP	主机名	server id	类型
manager	192.168.229.10	manager		管理节点
master	192.168.229.5	master1	1	主mysql(写)
candicate master	192.168.229.6	master2	2	从mysql(读)
slave	192.168.229.7	slave1	3	从mysql(读)

其中master对外提供写服务，备选master（实际的slave）提供读服务，slave也提供相关的读服务，一旦master宕机，将会把备选master提升为新的master，slave指向新的master，manager作为管理服务器。
2.配置hosts环境

[root@master1 ~]# vim /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
192.168.229.5 master1
192.168.229.6 master2
192.168.229.7 slave1
192.168.229.10 manager

3.关闭防火墙和selinux

systemctl stop firewalld
setenforce 0

4.同步时间
因为是下面是克隆而来的，所以时间是一致的。
5.配置epel源

yum -y install epel-release

5.安装MHA所依赖的软件包

yum -y install perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-Config-IniFiles ncftp perl-Params-Validate perl-CPAN perl-Test-Mock-LWP.noarch perl-LWP-Authen-Negotiate.noarch perl-devel perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker

6.克隆master1虚拟机
注意：克隆之后要修改IP地址和主机名，其实manager是不需要安装MySQL服务的，直接克隆master1只是为了方面。
克隆之前需要删除auto.cnf文件。

rm -rf /usr/local/mysql/data/auto.cnf
hostnamectl set-hostname 对应的主机名
bash
vim /etc/sysconfig/network-scripts/ifcfg-ens33
reboot

7.建立ssh无交互登录环境
(1)manager主机

[root@manager ~]# ssh-keygen -t rsa
[root@manager ~]# for i in master1 master2 slave1;do ssh-copy-id $i;done

(2)master1主机

[root@master1 ~]# ssh-keygen -t rsa
[root@master1 ~]# for i in manager master2 slave1;do ssh-copy-id $i;done

(3)master2主机

[root@master2 ~]# ssh-keygen -t rsa
[root@master2 ~]# for i in manager master1 slave1;do ssh-copy-id $i;done

(4)slave1主机：

[root@slave1 ~]# ssh-keygen -t rsa
[root@slave1 ~]# for i in manager master1 master2;do ssh-copy-id $i;done

(5)测试ssh无交互登录

[root@manager ~]# for i in master1 master2 slave1;do ssh $i hostname;done
master1
master2
slave1

在其他主机上执行同样的测试操作。

三、配置MySQL半同步复制

为了尽可能的减少主库硬件损坏宕机造成的数据丢失，因此配置MHA时建议配置成MySQL的半同步复制。
注意：mysql半同步插件是由谷歌提供，具体位置/usr/local/mysql/lib/plugin/下。

master用的是semisync_master.so;

slave用的是semisync_slave.so;

如果不清楚plugin的目录，可以用下面的方法查找。

mysql> show variables like '%plugin_dir%';
+---------------+------------------------------+
| Variable_name | Value                        |
+---------------+------------------------------+
| plugin_dir    | /usr/local/mysql/lib/plugin/ |
+---------------+------------------------------+
1 row in set (0.01 sec)

1.安装插件
分别在主从节点上安装相关的插件（master1、master2、slave1），在MySQL上安装插件需要数据库支持动态载入。
用下面的方法检测支持动态载入。

mysql> show variables like '%dynamic%';
+----------------------+-------+
| Variable_name        | Value |
+----------------------+-------+
| have_dynamic_loading | YES   |
+----------------------+-------+
1 row in set (0.01 sec)

所有MySQL数据库服务器，安装半同步插件(semisync_master.so，semisync_slave.so)。

mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
Query OK, 0 rows affected (0.00 sec)

mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';
Query OK, 0 rows affected (0.00 sec)

检查plugin是否已正确安装

mysql> show plugins;

或

mysql> select * from information_schema.plugins\G

查看半同步相关信息

mysql> show variables like '%rpl_semi_sync%';
+-------------------------------------------+------------+
| Variable_name                             | Value      |
+-------------------------------------------+------------+
| rpl_semi_sync_master_enabled              | OFF        |
| rpl_semi_sync_master_timeout              | 10000      |
| rpl_semi_sync_master_trace_level          | 32         |
| rpl_semi_sync_master_wait_for_slave_count | 1          |
| rpl_semi_sync_master_wait_no_slave        | ON         |
| rpl_semi_sync_master_wait_point           | AFTER_SYNC |
| rpl_semi_sync_slave_enabled               | OFF        |
| rpl_semi_sync_slave_trace_level           | 32         |
+-------------------------------------------+------------+
8 rows in set (0.00 sec)

可以看到半同复制插件已经安装，只是还没有启用，所以OFF。
2.修改my.cnf文件配置主从同步
注意：若主MySQL服务器已经存在，只是后期才搭建从MySQL服务器，在配置数据同步前应先将主MySQL服务器要同步的数据库拷贝到从MySQL服务器上（先在主MySQL上备份数据库，再用备份在从MySQL服务器上恢复）。
(1)master1主机

[root@master1 ~]# vim /etc/my.cnf
添加：
server_id=1
log_bin=mysql-bin
binlog_format=mixed
log_bin_index=mysql-bin.index
rpl_semi_sync_master_enabled=1
rpl_semi_sync_master_timeout=1000
rpl_semi_sync_slave_enabled=1
relay_log_purge=0
relay_log=relay-bin
relay_log_index=slave-relay-bin.index
[root@master1 ~]# systemctl restart mysqld

参数解释

rpl_semi_sync_master_enabled=1  #1表示启用，0表示关闭; 

rpl_semi_sync_master_timeout=10000  #毫秒单位，主服务器等待确认消息10秒后，不再等待，变为异步方式。

relay_log_purge=0  #禁止SQL线程在执行完一个relay log后自动将其删除。
对于MHA场景下，对于某些滞后从库的恢复依赖于其他从库的relay log，因此采取禁用自动删除功能。

(2)master2主机

[root@master2 ~]# vim /etc/my.cnf
添加：
server_id=2
log_bin=mysql-bin
binlog_format=mixed
log_bin_index=mysql-bin.index
rpl_semi_sync_master_enabled=1
rpl_semi_sync_master_timeout=1000
rpl_semi_sync_slave_enabled=1
relay_log_purge=0
relay_log=relay-bin
relay_log_index=slave-relay-bin.index
[root@master2 ~]# systemctl restart mysqld

(3)slave1主机

[root@slave1 ~]# vim /etc/my.cnf
添加：
server_id=3
log_bin=mysql-bin
relay_log=relay-bin
relay_log_index=slave-relay-bin.index
read_only=1
rpl_semi_sync_slave_enabled=1
[root@slave1 ~]# systemctl restart mysqld

3.查看半同步相关变量

mysql> show variables like '%rpl_semi_sync%';
+-------------------------------------------+------------+
| Variable_name                             | Value      |
+-------------------------------------------+------------+
| rpl_semi_sync_master_enabled              | ON         |
| rpl_semi_sync_master_timeout              | 1000       |
| rpl_semi_sync_master_trace_level          | 32         |
| rpl_semi_sync_master_wait_for_slave_count | 1          |
| rpl_semi_sync_master_wait_no_slave        | ON         |
| rpl_semi_sync_master_wait_point           | AFTER_SYNC |
| rpl_semi_sync_slave_enabled               | ON         |
| rpl_semi_sync_slave_trace_level           | 32         |
+-------------------------------------------+------------+
8 rows in set (0.00 sec)

4.查看半同步相关状态

mysql> show status like '%rpl_semi_sync%';
+--------------------------------------------+-------+
| Variable_name                              | Value |
+--------------------------------------------+-------+
| Rpl_semi_sync_master_clients               | 0     |
| Rpl_semi_sync_master_net_avg_wait_time     | 0     |
| Rpl_semi_sync_master_net_wait_time         | 0     |
| Rpl_semi_sync_master_net_waits             | 0     |
| Rpl_semi_sync_master_no_times              | 0     |
| Rpl_semi_sync_master_no_tx                 | 0     |
| Rpl_semi_sync_master_status                | ON    |
| Rpl_semi_sync_master_timefunc_failures     | 0     |
| Rpl_semi_sync_master_tx_avg_wait_time      | 0     |
| Rpl_semi_sync_master_tx_wait_time          | 0     |
| Rpl_semi_sync_master_tx_waits              | 0     |
| Rpl_semi_sync_master_wait_pos_backtraverse | 0     |
| Rpl_semi_sync_master_wait_sessions         | 0     |
| Rpl_semi_sync_master_yes_tx                | 0     |
| Rpl_semi_sync_slave_status                 | OFF   |
+--------------------------------------------+-------+
15 rows in set (0.00 sec)

关注几个状态参数值

rpl_semi_sync_master_status  #显示主服务是异步复制模式还是半同步复制模式;

rpl_semi_sync_master_clients：显示有多少个从服务器配置为半同步复制模式;

rpl_semi_sync_master_yes_tx：显示从服务器确认成功提交的数量;

rpl_semi_sync_master_no_tx：显示从服务器确认不成功提交的数量;

rpl_semi_sync_master_tx_avg_wait_time：事务因开启semi_sync，平均需要额外等待的时间;

rpl_semi_sync_master_net_avg_wait_time：事务进入等待队列后，到网络平均等待时间;

5.创建复制账号和管理账号
第一条grant命令是创建一个用于主从复制的帐号，在master1和master2的主机上创建即可。
第二条grant命令是创建MHA管理账号，所有mysql服务器上都需要执行。
MHA会在配置文件里要求能远程登录到数据库，所以要进行必要的赋权。
(1)master1主机

mysql> grant replication slave on *.* to mharep@'192.168.229.%' identified by 'Test123!';
Query OK, 0 rows affected, 1 warning (1.00 sec)

mysql> grant all on *.* to manager@'192.168.229.%' identified by 'Test123!';
Query OK, 0 rows affected, 1 warning (0.00 sec)

mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File             | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000001 |      746 |              |                  |                   |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

(2)master2主机

mysql> grant replication slave on *.* to mharep@'192.168.229.%' identified by 'Test123!';
Query OK, 0 rows affected, 1 warning (1.01 sec)

mysql> grant all on *.* to manager@'192.168.229.%' identified by 'Test123!';
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> change master to master_host='192.168.229.5',master_port=3306,master_user='mharep',master_password='Test123!',master_log_file='mysql-bin.000001',master_log_pos=746;
Query OK, 0 rows affected, 2 warnings (0.01 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: 192.168.229.5
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 746
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             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: 746
              Relay_Log_Space: 521
              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: 1
                  Master_UUID: 6e4c4718-8246-11eb-af6f-000c29b43d44
             Master_Info_File: /usr/local/mysql/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: 
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 
1 row in set (0.00 sec)

(3)slave1主机

mysql> grant all on *.* to manager@'192.168.229.%' identified by 'Test123!';
Query OK, 0 rows affected, 1 warning (0.01 sec)

mysql> change master to master_host='192.168.229.5',master_port=3306,master_user='mharep',master_password='Test123!',master_log_file='mysql-bin.000001',master_log_pos=746;
Query OK, 0 rows affected, 2 warnings (0.01 sec)

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

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.229.5
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 746
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             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: 746
              Relay_Log_Space: 521
              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: 1
                  Master_UUID: 6e4c4718-8246-11eb-af6f-000c29b43d44
             Master_Info_File: /usr/local/mysql/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: 
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 
1 row in set (0.00 sec)

6.查看master1的半同步状态

mysql> show status like '%rpl_semi_sync%';
+--------------------------------------------+-------+
| Variable_name                              | Value |
+--------------------------------------------+-------+
| Rpl_semi_sync_master_clients               | 2     |
| Rpl_semi_sync_master_net_avg_wait_time     | 0     |
| Rpl_semi_sync_master_net_wait_time         | 0     |
| Rpl_semi_sync_master_net_waits             | 0     |
| Rpl_semi_sync_master_no_times              | 1     |
| Rpl_semi_sync_master_no_tx                 | 2     |
| Rpl_semi_sync_master_status                | ON    |
| Rpl_semi_sync_master_timefunc_failures     | 0     |
| Rpl_semi_sync_master_tx_avg_wait_time      | 0     |
| Rpl_semi_sync_master_tx_wait_time          | 0     |
| Rpl_semi_sync_master_tx_waits              | 0     |
| Rpl_semi_sync_master_wait_pos_backtraverse | 0     |
| Rpl_semi_sync_master_wait_sessions         | 0     |
| Rpl_semi_sync_master_yes_tx                | 0     |
| Rpl_semi_sync_slave_status                 | OFF   |
+--------------------------------------------+-------+
15 rows in set (0.00 sec)

四、安装部署mysql-mha

mha包括manager节点和data节点。

data节点包括原有的MySQL复制结构中的主机，至少3台，即1主2从。
当master failover后，还能保证主从结构，只需安装node包。

manager节点运行监控脚本，负责monitoring和auto-failover。
需要安装node包和manager包。

1.安装所需压缩包
以下操作管理节点需要两个都安装，在3台数据库节点只要安装MHA的node节点。

软件下载：https://github.com/yoshinorim

(1)data节点
在所有MySQL数据库节点上安装mha4mysql-node-0.58.tar.gz

[root@master1 ~]# cd /usr/local/src/
[root@master1 src]# ls
mha4mysql-node-0.58.tar.gz
[root@master1 src]# tar zxf mha4mysql-node-0.58.tar.gz
[root@master1 src]# cd mha4mysql-node-0.58/
[root@master1 mha4mysql-node-0.58]# perl Makefile.PL
[root@master1 mha4mysql-node-0.58]# make && make install

其他两个数据节点也安装。
(2)manager节点
在管理节点两个都需要安装：mha4mysql-node-0.58.tar.gz和mha4mysql-manager-0.58.tar.gz。

[root@manager ~]# cd /usr/local/src/
[root@manager src]# ls
mha4mysql-manager-0.58.tar.gz  mha4mysql-node-0.58.tar.gz
[root@manager src]# tar zxf mha4mysql-node-0.58.tar.gz 
[root@manager src]# cd mha4mysql-node-0.58/
[root@manager mha4mysql-node-0.58]# perl Makefile.PL
[root@manager mha4mysql-node-0.58]# make && make install
[root@manager mha4mysql-node-0.58]# cd ..
[root@manager src]# tar zxf mha4mysql-manager-0.58.tar.gz
[root@manager src]# cd mha4mysql-manager-0.58/
[root@manager mha4mysql-manager-0.58]# perl Makefile.PL
[root@manager mha4mysql-manager-0.58]# make && make install

2.创建目录

[root@manager mha4mysql-manager-0.58]# mkdir /etc/masterha
[root@manager mha4mysql-manager-0.58]# mkdir -p /masterha/app1
[root@manager mha4mysql-manager-0.58]# mkdir /scripts
[root@manager mha4mysql-manager-0.58]# cp samples/conf/* /etc/masterha/
[root@manager mha4mysql-manager-0.58]# cp samples/scripts/* /scripts/

3.配置mha
与绝大多数Linux应用程序类似，MHA的正确使用依赖于合理的配置文件。MHA的配置文件与MySQL的my.cnf文件配置相似，采取的是param=value的方式来配置，配置文件位于管理节点，通常包括每一个mysql server的主机名，mysql用户名和密码，工作目录等。
编辑/etc/masterha/app1.conf

[root@manager mha4mysql-manager-0.58]# vim /etc/masterha/app1.cnf
[server default]
manager_workdir=/masterha/app1
manager_log=/masterha/app1/manager.log
user=manager
password=Test123!
ssh_user=root
repl_user=mharep
repl_password=Test123!
ping_interval=1

[server1]
hostname=192.168.229.5
port=3306
master_binlog_dir=/usr/local/mysql/data
candidate_master=1

[server2]
hostname=192.168.229.6
port=3306
master_binlog_dir=/usr/local/mysql/data
candidate_master=1

[server3]
hostname=192.168.229.7
port=3306
master_binlog_dir=/usr/local/mysql/data
no_master=1
[root@manager mha4mysql-manager-0.58]# >/etc/masterha/masterha_default.cnf  #清空文件内容

五、MHA Manager端常用操作

1.检查是否有下列文件，有则删除。
发生主从切换后，MHAmanager服务会自动停掉，且在manager_workdir(/masterha/app1）目录下面生成文件app1.failover.complete，若要重新启动MHA，必须先确保无此文件)，如果有这个提示，那么删除此文件。

/masterha/app1/app1.failover.complete [error]
[/usr/share/perl5/vendor_perl/MHA/MasterFailover.pm, ln298] Last failover was done at 2015/01/09 10:00:47.
Current time is too early to do failover again. If you want to do failover, manually remove /masterha/app1/app1.failover.complete and run this script again.

[root@manager ~]# cd /masterha/app1/
[root@manager app1]# ls
app1.failover.complete  manager.log
[root@manager app1]# rm -rf app1.failover.complete
[root@manager app1]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &

2.查看MHA复制检查
需要把master1设置成candidate的从服务器。
先从日志文件中过滤所需内容

[root@manager ~]# grep 'CHANGE' /masterha/app1/manager.log
Thu Mar 11 21:49:15 2021 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=746, MASTER_USER='mharep', MASTER_PASSWORD='xxx';
Thu Mar 11 21:49:16 2021 - [info]  Executed CHANGE MASTER.

根据内容在master1上执行操作

[root@master1 ~]# systemctl start mysqld

mysql> CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=746, MASTER_USER='mharep', MASTER_PASSWORD='Test123!';
Query OK, 0 rows affected, 2 warnings (0.01 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: 192.168.229.6
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 746
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             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: 746
              Relay_Log_Space: 521
              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: 2
                  Master_UUID: 465d6680-8245-11eb-83da-000c2947f84a
             Master_Info_File: /usr/local/mysql/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: 
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 
1 row in set (0.00 sec)

查看复制状态

[root@manager ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf

3.停止MHA

[root@manager ~]# masterha_stop --conf=/etc/masterha/app1.cnf
MHA Manager is not running on app1(2:NOT_RUNNING).

4.启动MHA

[root@manager ~]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 127122

当有slave节点宕掉时，默认是启动不了的，加上–ignore_fail_on_start，即使有节点宕掉也能启动MHA，如下：

# nohup masterha_manager --conf=/etc/masterha/app1.cnf --ignore_fail_on_start &>/tmp/mha_manager.log &

5.检查状态

[root@manager ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:127122) is running(0:PING_OK), master:192.168.229.6

6.检查日志

# tail -f /masterha/app1/manager.log

7.主从切换后续工作
重构：重构就是你的主挂了，切换到candidate master上，candidate master变成了主，因此重构的一种方案原主库修复成一个新的slave主库切换后，把原主库修复成新从库，然后重新执行以上5步。原主库数据文件完整的情况下，可通过以下方式找出最后执行的CHANGE MASTER命令：

[root@manager ~]# grep 'CHANGE' /masterha/app1/manager.log
Thu Mar 11 21:49:15 2021 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=746, MASTER_USER='mharep', MASTER_PASSWORD='xxx';
Thu Mar 11 21:49:16 2021 - [info]  Executed CHANGE MASTER.

[root@master1 ~]# mysql -uroot -pasd123

mysql> CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=746, MASTER_USER='mharep', MASTER_PASSWORD='Test123!';
Query OK, 0 rows affected, 2 warnings (0.01 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: 192.168.229.6
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000001
          Read_Master_Log_Pos: 746
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000001
             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: 746
              Relay_Log_Space: 521
              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: 2
                  Master_UUID: 465d6680-8245-11eb-83da-000c2947f84a
             Master_Info_File: /usr/local/mysql/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: 
                Auto_Position: 0
         Replicate_Rewrite_DB: 
                 Channel_Name: 
           Master_TLS_Version: 
1 row in set (0.00 sec)

启动manager

[root@manager ~]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 13666
[root@manager ~]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:127122) is running(0:PING_OK), master:192.168.229.6

注意：如果正常，会显示"PING_OK"，否则会显示"NOT_RUNNING"，这代表MHA监控没有开启。
定期删除中继日志
在配置主从复制中，slave上设置了参数relay_log_purge=0，所以slave节点需要定期删除中继日志，建议每个slave节点删除中继日志的时间错开。

crontab -e
0 5 * * * /usr/local/bin/purge_relay_logs --user=root --password=asd123 --port=3306 --disable_relay_log_purge >> /var/log/purge_relay.log 2>&1

六、配置VIP

1.vip配置有两种方式

(1)通过keepalived管理虚拟ip的浮动;

(2)通过脚本方式启动虚拟ip(即不需要keepalived或者heartbeat类似的软件);

2.keepalived方式管理虚拟ip
(1)下载软件并安装
两台master，准确的说一台是master，另外一台是备选master，在没有切换以前是slave。在master1和master2上安装软件包keepalived，安装keepalived软件包与服务控制。

[root@master1 ~]# cd /usr/local/src/
[root@master1 src]# wget https://www.keepalived.org/software/keepalived-2.2.0.tar.gz

(2)安装支持库
在编译安装Keepalived之前，必须先安装内核开发包kernel-devel以及openssl-devel、popt-devel等支持库。

[root@master1 src]# yum -y install kernel-devel popt-devel openssl-devel

(3)编译安装Keepalived
使用指定的linux内核位置对keepalived进行配置，并将安装路径指定为根目录，这样就无需额外创建链接文件了，配置完成后，依次执行make、make install进行安装。

[root@master1 src]# tar zxf keepalived-2.2.0.tar.gz
[root@master1 src]# cd keepalived-2.2.0/
[root@master1 keepalived-2.2.0]# ./configure --prefix=/ && make && make install

注意：若开启了防火墙，需要关闭防火墙或创建规则。

# firewall-cmd --direct --permanent --add-rule ipv4 filter OUTPUT 0 --in-interface ens33 --destination 224.0.0.18 --protocol vrrp -j ACCEPT
# firewall-cmd --direct --permanent --add-rule ipv4 filter INPUT 0 --in-interface ens33 --destination 224.0.0.18 --protocol vrrp -j ACCEPT
# firewall-cmd --reload

(4)master1修改Keepalived的配置文件

[root@master1 keepalived-2.2.0]# vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   router_id mysql-ha1
}

vrrp_instance VI_1 {
    state BACKUP
    interface ens33
    virtual_router_id 51
    priority 100
    nopreempt
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.229.100
    }
}
[root@master1 keepalived-2.2.0]# scp /etc/keepalived/keepalived.conf master2:/etc/keepalived/

(5)候选master2上修改Keepalived的配置文件

[root@master2 keepalived-2.2.0]# vim /etc/keepalived/keepalived.conf
! Configuration File for keepalived

global_defs {
   router_id mysql-ha2
}

vrrp_instance VI_1 {
    state BACKUP
    interface ens33
    virtual_router_id 51
    priority 50
    nopreempt
    advert_int 1
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    virtual_ipaddress {
        192.168.229.100
    }
}

(6)master1启动keepalived服务

[root@master1 keepalived-2.2.0]# systemctl start keepalived
[root@master1 keepalived-2.2.0]# ps -ef | grep keep
root      38671      1  0 15:43 ?        00:00:00 //sbin/keepalived -D
root      38672  38671  0 15:43 ?        00:00:00 //sbin/keepalived -D
root      39699   1545  0 15:44 pts/0    00:00:00 grep --color=auto keep
[root@master1 keepalived-2.2.0]# ip a show dev ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:b4:3d:44 brd ff:ff:ff:ff:ff:ff
    inet 192.168.229.5/24 brd 192.168.229.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet 192.168.229.100/32 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c8a4:4ff4:6676:26ef/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

(7)在候选master2上启动keepalived

[root@master2 keepalived-2.2.0]# systemctl start keepalived
[root@master2 keepalived-2.2.0]# ps -ef | grep keep
root      41770      1  0 15:46 ?        00:00:00 //sbin/keepalived -D
root      41771  41770  0 15:46 ?        00:00:00 //sbin/keepalived -D
root      42163   1546  0 15:46 pts/0    00:00:00 grep --color=auto keep

注意：上面两台服务器的keepalived都设置成BACKUP模式。
在keepalived中有2种模式

(1)master->backup模式
一旦主库宕机，虚拟ip会自动漂移到从库，当主库修复后，keepalived启动后，还会把虚拟ip抢占过来，即使设置了非抢占模式（nopreempt），抢占ip的动作也会发生。

(2)backup->backup模式
当主库宕机后虚拟ip会自动漂移到从库上，当原主库恢复和keepalived服务启动后，并不会抢占新主的虚拟ip，即使是优先级高于从库的优先级别，也不会发生抢占。

为了减少ip漂移次数，通常是把修复好的主库当做新的备库。
3.MHA引入keepalived
MySQL服务进程挂掉时通过MHA停止keepalived，要想把keepalived服务引入MHA，只需要修改切换时触发的脚本文件master_ip_failover即可，在该脚本中添加在master发生宕机时对keepalived的处理。
(1)编辑脚本/scripts/master_ip_failover

[root@manager ~]# cd /scripts/
[root@manager scripts]# ls
master_ip_failover  master_ip_online_change  power_manager  send_report
[root@manager scripts]# mv master_ip_failover master_ip_failover.bak
#把修改好的脚本传到此目录下。
[root@manager scripts]# mv master_ip_failover_keepalived master_ip_failover
[root@manager 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 = '192.168.229.100';  #vip
my $ssh_start_vip = "systemctl start keepalived.service";  #开启keepalived
my $ssh_stop_vip = "systemctl stop keepalived.service";  #关闭keepalived
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" ) {
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" ) {
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 \"`;
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 \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
return 0 unless ($ssh_user);
`ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
}
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";
}
[root@manager scripts]# chmod +x master_ip_failover

(2)接着在/etc/masterha/app1.cnf中调用故障切换脚本停止MHA

[root@manager scripts]# masterha_stop --conf=/etc/masterha/app1.cnf
Stopped app1 successfully.
[1]+  退出 1                nohup masterha_manager -conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log(工作目录：/masterha/app1)
(当前工作目录：/scripts)

(3)在配置文件/etc/masterha/app1.cnf中启用下面的参数

[root@manager scripts]# vim /etc/masterha/app1.cnf
#在[server default]下面添加：
master_ip_failover_script=/scripts/master_ip_failover

(4)启动MHA

[root@manager scripts]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 44207

(5)检查状态

[root@manager scripts]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:53816) is running(0:PING_OK), master:192.168.229.5

(6)再检查集群状态，看是否会报错。

[root@manager scripts]# masterha_check_repl --conf=/etc/masterha/app1.cnf
...
Sat Mar 13 16:10:55 2021 - [info] Slaves settings check done.
Sat Mar 13 16:10:55 2021 - [info] 
192.168.229.5(192.168.229.5:3306) (current master)
 +--192.168.229.6(192.168.229.6:3306)
 +--192.168.229.7(192.168.229.7:3306)

Sat Mar 13 16:10:55 2021 - [info] Checking replication health on 192.168.229.6..
Sat Mar 13 16:10:55 2021 - [info]  ok.
Sat Mar 13 16:10:55 2021 - [info] Checking replication health on 192.168.229.7..
Sat Mar 13 16:10:55 2021 - [info]  ok.
Sat Mar 13 16:10:55 2021 - [info] Checking master_ip_failover_script status:
Sat Mar 13 16:10:55 2021 - [info]   /scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.229.5 --orig_master_ip=192.168.229.5 --orig_master_port=3306 


IN SCRIPT TEST====systemctl stop keepalived.service==systemctl start keepalived.service===

Checking the Status of the script.. OK 
Sat Mar 13 16:10:55 2021 - [info]  OK.
Sat Mar 13 16:10:55 2021 - [warning] shutdown_script is not defined.
Sat Mar 13 16:10:55 2021 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

/scripts/master_ip_failover添加或者修改的内容意思是当主库数据库发生故障时，会触发MHA切换，MHA Manager会停掉主库上的keepalived服务，触发虚拟ip漂移到备选从库，从而完成切换。
当然可以在keepalived里面引入脚本，这个脚本监控mysql是否正常运行，如果不正常，则调用该脚本杀掉keepalived进程。
(7)测试：在master1上停止mysqld服务，到slave1查看slave的状态。

[root@master1 keepalived-2.2.0]# systemctl stop mysqld
mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.229.6
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 154
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
...

可以看出slave指向了新的master2服务器192.168.229.6
(8)查看VIP绑定
在192.168.229.5上查看vip绑定

[root@master1 keepalived-2.2.0]# ip a show dev ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:b4:3d:44 brd ff:ff:ff:ff:ff:ff
    inet 192.168.229.5/24 brd 192.168.229.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c8a4:4ff4:6676:26ef/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

在192.168.229.6上查看vip绑定

[root@master2 keepalived-2.2.0]# ip a show dev ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:47:f8:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.229.6/24 brd 192.168.229.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet 192.168.229.100/32 scope global ens33
       valid_lft forever preferred_lft forever
    inet6 fe80::c8a4:4ff4:6676:26ef/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::3f82:e9b9:240a:7e6/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

从上面的显示结果可以看出vip地址漂移到了192.168.229.6
(9)主从切换后续重构
原主库修复成一个新的slave主库，切换后，把原主库修复成新从库，原主库数据文件完整的情况下，可通过以下方式找出最后执行的CHANGE MASTER命令：

[root@manager app1]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 is stopped(2:NOT_RUNNING).
[1]+  完成                  nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log
[root@manager app1]# grep 'CHANGE' /masterha/app1/manager.log
...
Sat Mar 13 16:04:22 2021 - [info]  Executed CHANGE MASTER.
Sat Mar 13 16:12:03 2021 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000003', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='xxx';
Sat Mar 13 16:12:04 2021 - [info]  Executed CHANGE MASTER.

将192.168.229.5（原主库）修复成从库

[root@master1 keepalived-2.2.0]# systemctl start mysqld
[root@master1 keepalived-2.2.0]# mysql -uroot -ppwd123
mysql> CHANGE MASTER TO MASTER_HOST='192.168.229.6', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000003', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='Test123!';
Query OK, 0 rows affected, 2 warnings (0.00 sec)

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

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.229.6
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000003
          Read_Master_Log_Pos: 154
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000003
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
...
[root@centos3 ~]# /etc/init.d/keepalived start
Starting keepalived: [ OK ]
[root@centos3 ~]# /etc/init.d/keepalived status
keepalived (pid 6436) is running...

(10)启动mha manager

[root@manager app1]# rm -rf app1.failover.complete
[root@manager app1]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 65527
[root@manager app1]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:65527) is running(0:PING_OK), master:192.168.229.6
[root@manager app1]# masterha_check_repl --conf=/etc/masterha/app1.cnf
...
Sat Mar 13 16:19:15 2021 - [info] Slaves settings check done.
Sat Mar 13 16:19:15 2021 - [info] 
192.168.229.6(192.168.229.6:3306) (current master)
 +--192.168.229.5(192.168.229.5:3306)
 +--192.168.229.7(192.168.229.7:3306)

Sat Mar 13 16:19:15 2021 - [info] Checking replication health on 192.168.229.5..
Sat Mar 13 16:19:15 2021 - [info]  ok.
Sat Mar 13 16:19:15 2021 - [info] Checking replication health on 192.168.229.7..
Sat Mar 13 16:19:15 2021 - [info]  ok.
Sat Mar 13 16:19:15 2021 - [info] Checking master_ip_failover_script status:
Sat Mar 13 16:19:15 2021 - [info]   /scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.229.6 --orig_master_ip=192.168.229.6 --orig_master_port=3306 


IN SCRIPT TEST====systemctl stop keepalived.service==systemctl start keepalived.service===

Checking the Status of the script.. OK 
Sat Mar 13 16:19:15 2021 - [info]  OK.
Sat Mar 13 16:19:15 2021 - [warning] shutdown_script is not defined.
Sat Mar 13 16:19:15 2021 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

4.通过脚本实现VIP切换
通过脚本的方式管理VIP。这里修改/scripts/master_ip_failover，也可以使用其他的语言完成，比如php语言。
(1)如果使用脚本管理vip的话，需要手动在master2服务器上绑定一个vip。

[root@master2 ~]# systemctl stop keepalived.service
[root@master2 ~]# ifconfig ens33:0 192.168.229.100/24
[root@master2 ~]# ip a show dev ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:47:f8:4a brd ff:ff:ff:ff:ff:ff
    inet 192.168.229.6/24 brd 192.168.229.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet 192.168.229.100/24 brd 192.168.229.255 scope global secondary ens33:0
       valid_lft forever preferred_lft forever
    inet6 fe80::c8a4:4ff4:6676:26ef/64 scope link tentative noprefixroute dadfailed 
       valid_lft forever preferred_lft forever
    inet6 fe80::3f82:e9b9:240a:7e6/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

(2)在mha-manager上修改/scripts/master_ip_failover

[root@manager ~]# cd /scripts/
[root@manager scripts]# ls
master_ip_failover      master_ip_online_change  send_report
master_ip_failover.bak  power_manager
[root@manager scripts]# mv master_ip_failover master_ip_failover.bak1
#将修改好的脚本上传到此目录
[root@manager 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 = '192.168.229.100';  #vip
my $key = '0';
my $ssh_start_vip = "/sbin/ifconfig ens33:$key $vip";  #启用vip
my $ssh_stop_vip = "/sbin/ifconfig ens33:$key down";  #禁用vip
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" ) {

        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" ) {

        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 \"`;
        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 \"`;
}
# A simple system call that disable the VIP on the old_master
sub stop_vip() {
     return 0  unless  ($ssh_user);
    `ssh $ssh_user\@$orig_master_host \" $ssh_stop_vip \"`;
}

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";
}
[root@manager scripts]# chmod +x master_ip_failover

(3)停止MHA

[root@manager scripts]# masterha_stop --conf=/etc/masterha/app1.cnf
Stopped app1 successfully.
[1]+  退出 1                nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log(工作目录：/masterha/app1)
(当前工作目录：/scripts)

(4)启动MHA

[root@manager scripts]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 79546

(5)检查状态

[root@manager scripts]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:81494) is running(0:PING_OK), master:192.168.229.6

(6)再检查集群状态，看是否会报错。

[root@manager scripts]# masterha_check_repl --conf=/etc/masterha/app1.cnf
...
Sat Mar 13 16:31:08 2021 - [info] Slaves settings check done.
Sat Mar 13 16:31:08 2021 - [info] 
192.168.229.6(192.168.229.6:3306) (current master)
 +--192.168.229.5(192.168.229.5:3306)
 +--192.168.229.7(192.168.229.7:3306)

Sat Mar 13 16:31:08 2021 - [info] Checking replication health on 192.168.229.5..
Sat Mar 13 16:31:08 2021 - [info]  ok.
Sat Mar 13 16:31:08 2021 - [info] Checking replication health on 192.168.229.7..
Sat Mar 13 16:31:08 2021 - [info]  ok.
Sat Mar 13 16:31:08 2021 - [info] Checking master_ip_failover_script status:
Sat Mar 13 16:31:08 2021 - [info]   /scripts/master_ip_failover --command=status --ssh_user=root --orig_master_host=192.168.229.6 --orig_master_ip=192.168.229.6 --orig_master_port=3306 


IN SCRIPT TEST====/sbin/ifconfig ens33:0 down==/sbin/ifconfig ens33:0 192.168.229.100===

Checking the Status of the script.. OK 
Sat Mar 13 16:31:08 2021 - [info]  OK.
Sat Mar 13 16:31:08 2021 - [warning] shutdown_script is not defined.
Sat Mar 13 16:31:08 2021 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.

(7)测试：在master2上停掉mysql服务。

[root@master2 ~]# systemctl stop mysqld

(8)到slave1查看slave的状态

mysql> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: Waiting for master to send event
                  Master_Host: 192.168.229.5
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000004
          Read_Master_Log_Pos: 154
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000004
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
...

可以看出slave指向了新的master1服务器
(9)查看VIP

[root@master1 keepalived-2.2.0]# ip a show dev ens33
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:0c:29:b4:3d:44 brd ff:ff:ff:ff:ff:ff
    inet 192.168.229.5/24 brd 192.168.229.255 scope global noprefixroute ens33
       valid_lft forever preferred_lft forever
    inet 192.168.229.100/24 brd 192.168.229.255 scope global secondary ens33:0
       valid_lft forever preferred_lft forever
    inet6 fe80::c8a4:4ff4:6676:26ef/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

可以看到master2(原来的master)释放了VIP，master1(新的master)接管了VIP地址。
(10)主从切换后续工作
主库切换后，把原主库修复成新从库。

[root@manager scripts]# grep 'CHANGE' /masterha/app1/manager.log
...
Sat Mar 13 16:32:01 2021 - [info]  All other slaves should start replication from here. Statement should be: CHANGE MASTER TO MASTER_HOST='192.168.229.5', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000004', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='xxx';
Sat Mar 13 16:32:02 2021 - [info]  Executed CHANGE MASTER.
[1]+  完成                  nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log

master2上操作，指向master1（新主）

mysql> CHANGE MASTER TO MASTER_HOST='192.168.229.5', MASTER_PORT=3306, MASTER_LOG_FILE='mysql-bin.000004', MASTER_LOG_POS=154, MASTER_USER='mharep', MASTER_PASSWORD='Test123!';
Query OK, 0 rows affected, 2 warnings (0.01 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: 192.168.229.5
                  Master_User: mharep
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysql-bin.000004
          Read_Master_Log_Pos: 154
               Relay_Log_File: relay-bin.000002
                Relay_Log_Pos: 320
        Relay_Master_Log_File: mysql-bin.000004
             Slave_IO_Running: Yes
            Slave_SQL_Running: Yes
...

开启MHA

[root@manager scripts]# rm -rf /masterha/app1/app1.failover.complete
[root@manager scripts]# nohup masterha_manager --conf=/etc/masterha/app1.cnf &>/tmp/mha_manager.log &
[1] 89949
[root@manager scripts]# masterha_check_status --conf=/etc/masterha/app1.cnf
app1 (pid:89949) is running(0:PING_OK), master:192.168.229.5

为了防止脑裂发生，推荐生产环境采用脚本的方式来管理虚拟ip，而不是使用keepalived来完成。
总结：MHA软件由两部分组成，Manager工具包和Node工具包，具体的说明如下。 (1)manager工具包主要包括以下几个工具

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信息

(2)node工具包主要包括以下几个工具
这些工具通常由MHA Manager的脚本触发，无需人为操作。

save_binary_logs  #保存和复制master的二进制日志

apply_diff_relay_logs  #识别差异的中继日志事件并将其差异的事件应用于其他的slave

filter_mysqlbinlog  #去除不必要的ROLLBACK事件（MHA已不再使用这个工具）

purge_relay_logs  #清除中继日志（不会阻塞SQL线程）

(3)mysql必备技能

(1)MySQL架构
只有对MySQL架构有整体印象，才能不断的加深MySQL的理解。

(2)备份MySQL数据库
数据备份是DBA或运维工程师日常工作之一，用什么方式备份，在什么时间备份，使用什么策略备份。

(3)MySQL主从复制及读写分离
MySQL的主从复制及读写分离是DBA必备技能之一。

(4)MySQL/MariaDB数据库基于SSL实现主从复制
加强主从复制的安全性。

(5)MySQL高可用
数据的高可用如何保证？

(6)数据库Sharding的基本思想和切分策略
随着数据量的不断攀升，从性能和可维护的角度，需要进行一些Sharding，也就是数据库的切分，有垂直切分和水平切分。

(7)MySQL/MariaDB性能调整和优化技巧
掌握优化思路和技巧，对数据库的不断优化是一项长期工程。

现实如此呀

关注

0
点赞
踩
2

收藏

觉得还不错? 一键收藏
2
评论
MySQL高可用之MHA

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

扫一扫