目录
2.4.2 利用master节点中备份出来的lee.sql在slave2中拉平数据
一、Mysql 在服务器中的部署方法
在企业中90%的服务器操作系统均为Linux
在企业中对于Mysql的安装通常用源码编译的方式来进行
官网：http://www.mysql.com
1.1 在Linux下部署mysql
1.1.1 安装依赖性：
[root@mysql ~]# dnf install cmake gcc-c++ openssl-devel ncurses-devel.x86_64 libtirpc-devel-1.3.3-8.el9_4.x86_64.rpm rpcgen.x86_641.1.2 下载并解压源码包
[root@mysql ~]# tar zxf mysql-boost-5.7.44.tar.gz
[root@mysql ~]# cd /root/mysql-5.7.441.1.3 源码编译安装mysql
[root@mysql mysql-5.7.44]# cmake \
-DCMAKE_INSTALL_PREFIX=/usr/local/mysql \ #指定安装路径
-DMYSQL_DATADIR=/data/mysql \ #指定数据目录
-DMYSQL_UNIX_ADDR=/data/mysql/mysql.sock \ #指定套接字文件
-DWITH_INNOBASE_STORAGE_ENGINE=1 \ #指定启用INNODB存储引擎，默认用myisam
-DWITH_EXTRA_CHARSETS=all \ #扩展字符集
-DDEFAULT_CHARSET=utf8mb4 \ #指定默认字符集
-DDEFAULT_COLLATION=utf8mb4_unicode_ci \ #指定默认校验字符集
-DWITH_BOOST=/root/mysql-5.7.44/boost/boost_1_59_0/ #指定c++库依赖
[root@mysql mysql-5.7.44]# make -j2 #-j2 #表示有几个核心就跑几个进程
[root@mysql mysql-5.7.44# make install注意：当cmake出错后如果想重新检测，删除 mysql-5.7.44 中 CMakeCache.txt即可
1.1.4 部署mysql
#生成启动脚本
[root@mysql ~]# dnf install initscripts-10.11.6-1.el9.x86_64 -y
[root@mysql ~]# cd /usr/local/mysql/support-files/
[root@mysql support-files]# cp mysql.server /etc/init.d/mysqld
#修改环境变量
[root@mysql ~]# vim ~/.bash_profile
PATH=$PATH:$HOME/bin:/usr/local/mysql/bin
[root@mysql ~]# source ~/.bash_profile
#生成配置文件
[root@mysql support-files]# yum install mariadb-connector-c-config-3.2.6-
1.el9_0.noarch -y
[root@mysql my.cnf.d]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql #指定数据目录
socket=/data/mysql/mysql.sock #指定套接字
symbolic-links=0 #数据只能存放到数据目录中，禁止链接到数据目录
#数据库初始化建立mysql基本数据
[root@mysql ~]# mysqld --initialize --user=mysql
[root@mysql ~]# /etc/init.d/mysqld start
[root@mysql ~]# chkconfig mysqld on
#数据库安全初始化
[root@mysql ~]# mysql_secure_installation
Securing the MySQL server deployment.
Enter password for user root: #输入当前密码
The existing password for the user account root has expired. Please set a new
password.
New password: #输入新密码
Re-enter new password: #重复密码
VALIDATE PASSWORD PLUGIN can be used to test passwords
and improve security. It checks the strength of password
and allows the users to set only those passwords which are
secure enough. Would you like to setup VALIDATE PASSWORD plugin?
Press y|Y for Yes, any other key for No: no #是否启用密码插件
Using existing password for root.
Change the password for root ? ((Press y|Y for Yes, any other key for No) : no #是否要重置密码
... skipping.
By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production
environment.
Remove anonymous users? (Press y|Y for Yes, any other key for No) : y
Success.
Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.
Disallow root login remotely? (Press y|Y for Yes, any other key for No) : y
Success.
By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production
environment.
Remove test database and access to it? (Press y|Y for Yes, any other key for No)
: y
- Dropping test database...
Success.
- Removing privileges on test database...
Success.
Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.
Reload privilege tables now? (Press y|Y for Yes, any other key for No) : y
[root@mysql ~]# mysql -uroot -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 4
Server version: 5.7.44-log Source distribution
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
mysql> SHOW DATABASES;
+--------------------+
| Database |
+--------------------+
| information_schema |
| mysql |
| performance_schema |
| sys |
+--------------------+
4 rows in set (0.00 sec)二、mysql的主从复制
2.1概述
主从复制是指将主数据库的DDL和 DML操作通过二进制日志传到从库服务器中，然后在从库上对这些日志重新执行(也叫重做)，从而使得从库和主库的数据保持同步
MySQL支持一台主库同时向多台从库进行复制，从库同时也可以作为其他从服务器的主库，实现链状复制。
MySQL复制的优点主要包含以下三个方面:
-
主库出现问题，可以快速切换到从库提供服务。
-
实现读写分离，降低主库的访问压力。
-
可以在从库中执行备份，以避免备份期间影响主库服务。
2.2.原理
三个线程
实际上主从同步的原理就是基于 binlog 进行数据同步的。在主从复制过程中，会基于3 个线程来操作，一个主库线程，两个从库线程.
二进制日志转储线程（Binlog dump thread）是一个主库线程。当从库线程连接的时候， 主库可以 将二进制日志发送给从库，当主库读取事件（Event）的时候，会在 Binlog 上加锁，读取完成之后，再将锁释放掉。
从库 I/O 线程会连接到主库，向主库发送请求更新 Binlog。这时从库的 I/O 线程就可以读取到主库的二进制日志转储线程发送的 Binlog 更新部分，并且拷贝到本地的中继日志 （Relay log）。
从库 SQL 线程会读取从库中的中继日志，并且执行日志中的事件，将从库中的数据与主库保持同步。
复制步骤
主库发生增删改等相关操作以及执行DDL语句的时候，将所有的数据变更写入binlog（二进制）日志当中。从库中的IO线程发起请求来连接master数据库，读取binlog日志并返回，写入slave数据库中的中继日志（Relay log），DQLthread读取中继日志，把中继日志的数据变化反映到自身的数据变化，从而保证主从数据一致
具体操作
1.slaves端中设置了master端的ip，用户，日志，和日志的Position，通过这些信息取得master的认证及信息
2.master端在设定好binlog启动后会开启binlog dump的线程
3.master端的binlog dump把二进制的更新发送到slave端的
4.slave端开启两个线程，一个是I/O线程，一个是sql线程，
i/o线程用于接收master端的二进制日志，此线程会在本地打开relaylog中继日志，并且保存 到本地磁盘
sql线程读取本地relog中继日志进行回放
5.什么时候我们需要多个slave？
当读取的而操作远远高与写操作时。我们采用一主多从架构
数据库外层接入负载均衡层并搭配高可用机制
2.3 配置主从复制
2.3.1 master端
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
symbolic-links=0
log-bin=mysql-bin
server-id=1
[root@mysql ~]# /etc/init.d/mysqld restart
[root@mysql ~]# mysql -uroot -p
mysql> CREATE USER 'yu'@'%' IDENTIFIED BY '123'; ##生成专门用来做复制的用户，此用户是用于slave端做认证用
mysql> GRANT REPLICATION SLAVE ON *.* TO yu@'%'; ##对这个用户进行授权
mysql> show master status;
+------------------+----------+--------------+------------------+-------------------+
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+------------------+----------+--------------+------------------+-------------------+
| mysql-bin.000002 | 427 | | | |
+------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)2.3.2 slave端
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
symbolic-links=0
server-id=2
[root@mysql ~]# /etc/init.d/mysqld restart
[root@mysql ~]# mysql -uroot -p
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160',MASTER_USER='yu',MASTER_PASSWORD='123',MASTER_LOG_FILE='mysql-bin.000002',MASTER_LOG_POS=427;
mysql> start slave;
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 172.25.254.160
Master_User: yu
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000002
Read_Master_Log_Pos: 427
Relay_Log_File: mysqlnode-relay-bin.000005
Relay_Log_Pos: 640
Relay_Master_Log_File: mysql-bin.000002
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: 427
Relay_Log_Space: 1017
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: 10
Master_UUID: 41a43bec-6031-11ef-bee5-000c2961a907
Master_Info_File: /data/mysql/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)2.4 当有数据时添加slave2
2.4.1 从master节点备份数据
#产环境中备份时需要锁表，保证备份前后的数据一致
mysql> FLUSH TABLES WITH READ LOCK;
[root@mysql ~]# mysqldump -uroot -pyu test1 > test1.sql
[root@mysql ~]# scp test1.sql root@172.25.254.180:/mnt/2.4.2 利用master节点中备份出来的lee.sql在slave2中拉平数据
[root@mysqlnode2 ]# cd /mnt/
[root@mysqlnode2 mnt]# mysql -uroot -p123 -e "create database test1;"
[root@mysqlnode2 mnt]# mysql -uroot -p123 test1 < test1.sql
#配置slave2的slave功能
[root@mysqlnode2 ]# mysql -uroot -p
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160',MASTER_USER='yu',MASSTER_PASSWORD='123',MASTER_LOG_FILE='mysql-bin.000002', MASTER_LOG_POS=1554;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
mysql>
mysql>
mysql>
mysql> start slave;
Query OK, 0 rows affected (0.00 sec)
mysql>
mysql>
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 172.25.254.160
Master_User: yu
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.000002
Read_Master_Log_Pos: 154
Relay_Log_File: mysqlnode2-relay-bin.000002
Relay_Log_Pos: 320
Relay_Master_Log_File: mysql-bin.000002
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: 154
Relay_Log_Space: 532
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: 10
Master_UUID: 41a43bec-6031-11ef-bee5-000c2961a907
Master_Info_File: /data/mysql/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)2.5 延迟复制
延迟复制时用来控制sql线程的，和i/o线程无关
这个延迟复制不是i/o线程过段时间来复制，i/o是正常工作的
是日志已经保存在slave端了，那个sql要等多久进行回放
#在slave端
mysql> stop slave sql_thread;
Query OK, 0 rows affected (0.00 sec)
mysql> change master to master_delay=60;
Query OK, 0 rows affected (0.01 sec)
mysql> start slave sql_thread;
Query OK, 0 rows affected (0.00 sec)
mysql> show slave status\G;
*************************** 1. row ***************************
Master_Server_Id: 1
Master_UUID: 41a43bec-6031-11ef-bee5-000c2961a907
Master_Info_File: /data/mysql/master.info
SQL_Delay: 60
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State: Slave has read all relay log; waiting for more updates
Master_Retry_Count: 864002.6 慢查询日志
慢查询，顾名思义，执行很慢的查询
当执行SQL超过long_query_time参数设定的时间阈值（默认10s）时，就被认为是慢查询，这个SQL语句就是需要优化的
慢查询被记录在慢查询日志里
慢查询日志默认是不开启的
如果需要优化SQL语句，就可以开启这个功能，它可以让你很容易地知道哪些语句是需要优化的
开启慢查询日志
mysql> SET GLOBAL slow_query_log=ON;
Query OK, 0 rows affected (0.00 sec)
mysql> SET long_query_time=4;
Query OK, 0 rows affected (0.00 sec)
mysql> SHOW VARIABLES like "long%";
+-----------------+----------+
| Variable_name | Value |
+-----------------+----------+
| long_query_time | 4.000000 |
+-----------------+----------+
1 row in set (0.00 sec)
mysql> SHOW VARIABLES like "slow%";
+---------------------+----------------------------------+
| Variable_name | Value |
+---------------------+----------------------------------+
| slow_launch_time | 2 |
| slow_query_log | ON | ##慢查询日志开启
| slow_query_log_file | /data/mysql/mysql-node1-slow.log |
+---------------------+----------------------------------+
3 rows in set (0.01 sec)2.7 mysql的并行复制
查看slave中的线程信息
mysql> show processlist;
+----+-------------+-----------+-------+---------+------+--------------------------------------------------------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+-------------+-----------+-------+---------+------+--------------------------------------------------------+------------------+
| 1 | system user | | NULL | Connect | 3528 | Waiting for master to send event | NULL |
| 2 | system user | | NULL | Connect | 2391 | Slave has read all relay log; waiting for more updates | NULL |
| 4 | root | localhost | test1 | Query | 0 | starting | show processlist |
+----+-------------+-----------+-------+---------+------+--------------------------------------------------------+------------------+
3 rows in set (0.00 sec)默认情况下slave中使用的是sql单线程回放
在master中时多用户读写，如果使用sql单线程回放那么会造成组从延迟严重
开启MySQL的多线程回放可以解决上述问题
在slaves中设定
[root@mysqlnode1 ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=2
gtid_mode=ON
enforce-gtid-consistency=ON
slave-parallel-type=LOGICAL_CLOCK #基于组提交，
slave-parallel-workers=16 #开启线程数量
master_info_repository=TABLE #master信息在表中记录，默认记录在/data/mysql//master.info
relay_log_info_repository=TABLE #回放日志信息在表中记录，默认记录在/data/mysql/relay-log.info
relay_log_recovery=ON #日志回放恢复功能开启
[root@mysqlnode1 ~]# /etc/init.d/mysql start
Starting MySQL. SUCCESS!
[root@mysqlnode ~]# /etc/init.d/mysqld restart
Shutting down MySQL.. SUCCESS!
Starting MySQL. SUCCESS!
[root@mysqlnode ~]# mysql -uroot -p123
mysql> show processlist;
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
| Id | User | Host | db | Command | Time | State | Info |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
| 2 | system user | | NULL | Connect | 26 | Slave has read all relay log; waiting for more updates | NULL |
| 3 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 5 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 6 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 7 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 8 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 9 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 10 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 11 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 12 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 13 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 14 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 15 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 16 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 17 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 18 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 19 | system user | | NULL | Connect | 26 | Waiting for an event from Coordinator | NULL |
| 20 | root | localhost | NULL | Query | 0 | starting | show processlist |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
18 rows in set (0.00 sec)三、半同步模式
3.1半同步模式原理
1.用户线程写入完成后master中的dump会把日志推送到slave端
2.slave中的io线程接收后保存到relaylog中继日志
3.保存完成后slave向master端返回ack
4.在未接受到slave的ack时master端时不做提交的，一直处于等待当收到ack后提交到存储引擎
5.在5.6版本中用到的时after_commit模式，after_commit模式时先提交在等待ack返回后输出ok
3.2 gtid模式
当为启用gtid时我们要考虑的问题
在master端的写入时多用户读写，在slave端的复制时单线程日志回放，所以slave端一定会延迟与master端
这种延迟在slave端的延迟可能会不一致，当master挂掉后slave接管，一般会挑选一个和master延迟日志最接近的充当新的master
那么为接管master的主机继续充当slave角色并会指向到新的master上，作为其slave
这时候按照之前的配置我们需要知道新的master上的pos的id，但是我们无法确定新的master和slave之间差多少
当激活GITD之后
当master出现问题后，slave2和master的数据最接近，会被作为新的master
slave1指向新的master，但是他不会去检测新的master的pos id，只需要继续读取自己gtid_next即可。
设置gtid
#在master端和slave端开启gtid模式
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=1
log-bin=mysql-bin
gtid_mode=ON
enforce-gtid-consistency=ON
symbolic-links=0
[root@mysql ~]# /etc/init.d/mysqld restart
[root@mysqlnode2 ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=2
log-bin=mysql-bin
gtid_mode=ON
enforce-gtid-consistency=ON
symbolic-links=0
[root@mysqlnode2 ~]# /etc/init.d/mysqld restart
[root@mysqlnode1 ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=3
log-bin=mysql-bin
gtid_mode=ON
enforce-gtid-consistency=ON
symbolic-links=0
[root@mysqlnode1 ~]# /etc/init.d/mysqld restart
#停止slave端
[root@mysqlnode2 ~]# mysql -p
mysql> stop slave;
Query OK, 0 rows affected (0.00 sec)
[root@mysqlnode1 ~]# mysql -p
mysql> stop slave;
Query OK, 0 rows affected (0.01 sec)
#开启slave端的gtid
mysql> stop slave;
Query OK, 0 rows affected (0.00 sec)
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160', MASTER_USER='yu',MASTER_PASSWORD='123', MASTER_AUTO_POSITION=1;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 172.25.254.160
Master_User: yu
Master_Port: 3306
Connect_Retry: 60
Master_Log_File:
Read_Master_Log_Pos: 4
Relay_Log_File: mysqlnode-relay-bin.000001
Relay_Log_Pos: 4
Relay_Master_Log_File:
Slave_IO_Running: No
Slave_SQL_Running: No
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: 0
Relay_Log_Space: 154
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: NULL
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: 10
Master_UUID: 41a43bec-6031-11ef-bee5-000c2961a907
Master_Info_File: mysql.slave_master_info
SQL_Delay: 0
SQL_Remaining_Delay: NULL
Slave_SQL_Running_State:
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: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)3.3 启用半同步模式
在master端配置启用半同步模式
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=1
log-bin=mysql-bin
gtid_mode=ON
enforce-gtid-consistency=ON
rpl_semi_sync_master_enabled=1 #开启半同步功能
symbolic-links=0
[root@mysql ~]# mysql -p
#安装半同步插件
mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
#查看插件情况
mysql> SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%semi%';
+----------------------+---------------+
| PLUGIN_NAME | PLUGIN_STATUS |
+----------------------+---------------+
| rpl_semi_sync_master | ACTIVE |
+----------------------+---------------+
1 row in set (0.00 sec)
#打开半同步功能
mysql> SET GLOBAL rpl_semi_sync_master_enabled = 1;
mysql> SHOW VARIABLES LIKE 'rpl_semi_sync%';
+-------------------------------------------+------------+
| Variable_name | Value |
+-------------------------------------------+------------+
| rpl_semi_sync_master_enabled | ON |
| 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 |
+-------------------------------------------+------------+
6 rows in set (0.00 sec)
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 |
+--------------------------------------------+-------+
14 rows in set (0.00 sec)
[root@mysqlnode2 ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=1
log-bin=mysql-bin
gtid_mode=ON
enforce-gtid-consistency=ON
rpl_semi_sync_master_enabled=1 #开启半同步功能
symbolic-links=0
[root@mysql-node2 ~]# mysql -p
mysql> INSTALL PLUGIN rpl_semi_sync_slave SONAME 'semisync_slave.so';
Query OK, 0 rows affected (0.01 sec)
mysql> SET GLOBAL rpl_semi_sync_slave_enabled =1;
Query OK, 0 rows affected (0.00 sec)
mysql> STOP SLAVE IO_THREAD; #重启io线程，半同步才能生效
Query OK, 0 rows affected (0.01 sec)
mysql> START SLAVE IO_THREAD; #重启io线程，半同步才能生效
Query OK, 0 rows affected (0.00 sec)
mysql> SHOW VARIABLES LIKE 'rpl_semi_sync%';
+---------------------------------+-------+
| Variable_name | Value |
+---------------------------------+-------+
| rpl_semi_sync_slave_enabled | ON |
| rpl_semi_sync_slave_trace_level | 32 |
+---------------------------------+-------+
2 rows in set (0.01 sec)
mysql> SHOW STATUS LIKE 'Rpl_semi_sync%';
+----------------------------+-------+
| Variable_name | Value |
+----------------------------+-------+
| Rpl_semi_sync_slave_status | ON |
+----------------------------+-------+
1 row in set (0.01 sec)四、mysql高可用之组复制 (MGR)
MySQL Group Replication(简称 MGR )是 MySQL 官方于 2016 年 12 月推出的一个全新的高可用与高扩展的解决方案
组复制是 MySQL 5.7.17 版本出现的新特性，它提供了高可用、高扩展、高可靠的 MySQL 集群服务
MySQL 组复制分单主模式和多主模式，传统的mysql复制技术仅解决了数据同步的问题，
MGR 对属于同一组的服务器自动进行协调。对于要提交的事务，组成员必须就全局事务序列中给定事务的顺序达成一致
提交或回滚事务由每个服务器单独完成，但所有服务器都必须做出相同的决定
如果存在网络分区，导致成员无法达成事先定义的分割策略，则在解决此问题之前系统不会继续进行，这是一种内置的自动裂脑保护机制
MGR由组通信系统( Group Communication System ，GCS ) 协议支持
该系统提供故障检测机制、组成员服务以及安全且有序的消息传递
4.1 组复制流程
首先我们将多个节点共同组成一个复制组，在执行读写（RW）事务的时候，需要通过一致性协议层（Consensus 层）的同意，也就是读写事务想要进行提交，必须要经过组里“大多数人”（对应 Node 节点）的同意，大多数指的是同意的节点数量需要大于 （N/2+1），这样才可以进行提交，而不是原发起方一个说了算。而针对只读（RO）事务则不需要经过组内同意，直接 提交 即可
注意：节点数量不能超过9台
4.2 组复制单主和多主模式
single-primary mode(单写或单主模式)
单写模式 group 内只有一台节点可写可读，其他节点只可以读。当主服务器失败时，会自动选择新的主服务器
multi-primary mode(多写或多主模式)
组内的所有机器都是 primary 节点，同时可以进行读写操作，并且数据是最终一致的。
4.3 实现mysql组复制
#在mysql中
[root@mysql~]# rm -fr /data/mysql/
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
symbolic-links=0
server-id=1 #配置server唯一标识号
disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY" #禁用指定存储引擎
gtid_mode=ON #启用全局事件标识
enforce_gtid_consistency=ON #强制gtid一致
master_info_repository=TABLE #复制事件数据到表中而不记录在数据目录中
relay_log_info_repository=TABLE
binlog_checksum=NONE #禁止对二进制日志校验
log_slave_updates=ON #打开数据库中继，
#当slave中sql线程读取日志后也会写入到自己的binlog中
log_bin=binlog #重新指定log名称
binlog_format=ROW #使用行日志格式
plugin_load_add='group_replication.so' #加载组复制插件
transaction_write_set_extraction=XXHASH64 #把每个事件编码为加密散列
group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" #通知插件正式加入
#或创建的组名
#名称为uuid格式
group_replication_start_on_boot=off #在server启动时不自动启动组复制
group_replication_local_address="172.25.254.160:33061" #指定插件接受其他成员的信息端口
group_replication_group_seeds="172.25.254.160:33061,172.25.254.170:33061,172.25.254.180:33061" #本地地址允许访问成员列表
group_replication_ip_whitelist="172.25.254.0/24,127.0.0.1/8" #主机白名单
#不随系统自启而启动，只在初始成员主机中手动开启，
#需要在两种情况下做设定：1.初始化建组时 2.关闭并重新启动整个组时
group_replication_bootstrap_group=off
group_replication_single_primary_mode=OFF #使用多主模式
group_replication_enforce_update_everywhere_checks=ON #组同步中有任何改变检测更新
group_replication_allow_local_disjoint_gtids_join=1 #放弃自己信息以master事件为主
[root@mysql ~]# mysqld --user=mysql --initialize
[root@mysql ~]# /etc/init.d/mysqld start
[root@mysql ~]# mysql -p
mysql> SET SQL_LOG_BIN=0;
Query OK, 0 rows affected (0.00 sec)
mysql> CREATE USER rpl_user@'%' IDENTIFIED BY 'lee';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
mysql> SET SQL_LOG_BIN=1;
Query OK, 0 rows affected (0.00 sec)
mysql> CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='lee' FOR CHANNEL 'group_replication_recovery';
Query OK, 0 rows affected, 2 warnings (0.00 sec)
mysql> SET GLOBAL group_replication_bootstrap_group=ON; #用以指定初始成员，值在第一台主机中执行
Query OK, 0 rows affected (0.00 sec)
mysql> START GROUP_REPLICATION;
Query OK, 0 rows affected, 1 warning (2.19 sec)
mysql> SET GLOBAL group_replication_bootstrap_group=OFF;
Query OK, 0 rows affected (0.00 sec)#在复制配置文件到myqlnode1和mysqlnode2中
[root@mysql ~]# scp /etc/my.cnf root@172.25.254.170:/etc/my.cnf
[root@mysql ~]# scp /etc/my.cnf root@172.25.254.180:/etc/my.cnf
[root@mysqlnode ~]# cat /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
symbolic-links=0
server-id=20
disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY"
gtid_mode=ON
enforce-gtid-consistency=ON
master_info_repository=TABLE
relay_log_info_repository=TABLE
binlog_checksum=NONE
log_slave_updates=ON
log_bin=binlog
binlog_format=ROW
plugin_load_add='group_replication.so'
transaction_write_set_extraction=XXHASH64
group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
group_replication_start_on_boot=off
group_replication_local_address="172.25.254.170:33061"
group_replication_group_seeds="172.25.254.160:33061,172.25.254.170:33061,172.25.254.180:33061"
group_replication_ip_whitelist="172.25.254.0/24,127.0.0.1/8"
group_replication_bootstrap_group=off
group_replication_single_primary_mode=OFF
group_replication_enforce_update_everywhere_checks=ON
group_replication_allow_local_disjoint_gtids_join=1
[root@mysqlnode1 ~]# mysqld --user=mysql --initialize
[root@mysqlnode1 ~]# /etc/init.d/mysqld start
#配置sql
[root@mysqlnode1 & 2 ~]# mysql -plee
mysql> SET SQL_LOG_BIN=0;
Query OK, 0 rows affected (0.00 sec)
mysql> CREATE USER rpl_user@'%' IDENTIFIED BY 'lee';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
mysql> SET SQL_LOG_BIN=1;
Query OK, 0 rows affected (0.00 sec)
mysql> CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='lee' FOR CHANNEL 'group_replication_recovery';
Query OK, 0 rows affected, 2 warnings (0.00 sec)
mysql> START GROUP_REPLICATION;
Query OK, 0 rows affected, 1 warning (2.19 sec)
mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------------+-------------+--------------+
| CHANNEL_NAME | MEMBER_ID | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------------+-------------+--------------+
| group_replication_applier | 10c193cb-61e5-11ef-8034-000c29dafdd4 | mysqlnode.yu.com | 3306 | ONLINE |
| group_replication_applier | 5ad8bc27-61e4-11ef-b053-000c2961a907 | mysql.yu.com | 3306 | ONLINE |
| group_replication_applier | af57f28d-61e5-11ef-a663-000c29a08182 | mysqlnode2.yu.com | 3306 | ONLINE |
+---------------------------+--------------------------------------+-------------------+-------------+--------------+
3 rows in set (0.00 sec)五、mysql-router（mysql路由）
MySQL Router
是一个对应用程序透明的InnoDB Cluster连接路由服务，提供负载均衡、应用连接故障转移和客户端路由。
利用路由器的连接路由特性，用户可以编写应用程序来连接到路由器，并令路由器使用相应的路由策略来处理连接，使其连接到正确的MySQL数据库服务器
Mysql route的部署方式
我们需要在所有的数据库主机之外再开一台主机mysql-router
#安装mysql-router
[root@mysql-router ~]# rpm -ivh mysql-router-community-8.4.0-1.el7.x86_64.rpm
#配置mysql-router
[root@mysql-router ~]# vim /etc/mysqlrouter/mysqlrouter.conf
[routing:ro]
bind_address = 0.0.0.0
bind_port = 7001
destinations = 172.25.254.160:3306,172.25.254.170:3306,172.25.254.180:3306
routing_strategy = round-robin
[routing:rw]
bind_address = 0.0.0.0
bind_port = 7002
destinations = 172.25.254.160:3306,172.25.254.170:3306,172.25.254.180:3306
routing_strategy = first-available
[root@mysql-router ~]# systemctl start mysqlrouter.service注意：mysql router 并不能限制数据库的读写，访问分流
六、mysql高可用之MHA
6.1 MHA概述
为什么要用MHA？
Master的单点故障问题
什么是 MHA？
MHA（Master High Availability）是一套优秀的MySQL高可用环境下故障切换和主从复制的软件。
MHA 的出现就是解决MySQL 单点的问题。
MySQL故障切换过程中，MHA能做到0-30秒内自动完成故障切换操作。
MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用。
MHA 的组成
MHA由两部分组成:MHAManager (管理节点) MHA Node (数据库节点),
MHA Manager 可以单独部署在一台独立的机器上管理多个master-slave集群，也可以部署在一台slave 节点上。
MHA Manager 会定时探测集群中的 master 节点。
当 master 出现故障时，它可以自动将最新数据的 slave 提升为新的 master， 然后将所有其他的slave 重新指向新的 master。
MHA 的特点
自动故障切换过程中，MHA从宕机的主服务器上保存二进制日志，最大程度的保证数据不丢失
使用半同步复制，可以大大降低数据丢失的风险，如果只有一个slave已经收到了最新的二进制日志，MHA可以将最新的二进制日志应用于其他所有的slave服务器上，因此可以保证所有节点的数据一致性
目前MHA支持一主多从架构，最少三台服务，即一主两从
故障切换备选主库的算法
1．一般判断从库的是从（position/GTID）判断优劣，数据有差异，最接近于master的slave，成为备选主。
2．数据一致的情况下，按照配置文件顺序，选择备选主库。
3．设定有权重（candidate_master=1），按照权重强制指定备选主。
（1）默认情况下如果一个slave落后master 100M的relay logs的话，即使有权重，也会失效。
（2）如果check_repl_delay=0的话，即使落后很多日志，也强制选择其为备选主。
MHA工作原理
目前MHA主要支持一主多从的架构，要搭建MHA,要求一个复制集群必须最少有3台数据库服务器，一主二从，即一台充当Master，台充当备用Master，另一台充当从库。
MHA Node 运行在每台 MySQL 服务器上
MHAManager 会定时探测集群中的master 节点
当master 出现故障时，它可以自动将最新数据的slave 提升为新的master
然后将所有其他的slave 重新指向新的master，VIP自动漂移到新的master。
整个故障转移过程对应用程序完全透明。
6.2 MHA部署实施
6.2.1 搭建主两从架构
#在master节点中
[root@mysql ~]# /etc/init.d/mysqld stop
[root@mysql ~]# rm -fr /data/mysql/*
[root@mysql ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=1
log-bin=mysql-bin
gtid_mode=ON
log_slave_updates=ON
enforce-gtid-consistency=ON
symbolic-links=0
[root@mysql ~]# mysqld --user mysql --initialize
[root@mysql ~]# /etc/init.d/mysqld start
[root@mysql ~]# mysql_secure_installation
[root@mysql ~]# mysql -p
mysql> CREATE USER 'yu'@'%' IDENTIFIED BY '123';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT REPLICATION SLAVE ON *.* TO yu@'%';
Query OK, 0 rows affected (0.00 sec)
mysql> INSTALL PLUGIN rpl_semi_sync_master SONAME 'semisync_master.so';
Query OK, 0 rows affected (0.02 sec)
mysql> SET GLOBAL rpl_semi_sync_master_enabled = 1;
Query OK, 0 rows affected (0.00 sec)
#在slave1和slave2中
[root@mysqlnode1 & 2 ~]# /etc/init.d/mysqld stop
[root@mysqlnode1 & 2 ~]# rm -fr /data/mysql/*
[root@mysqlnode1 & 2 ~]# vim /etc/my.cnf
[mysqld]
datadir=/data/mysql
socket=/data/mysql/mysql.sock
server-id=1
log-bin=mysql-bin
gtid_mode=ON
log_slave_updates=ON
enforce-gtid-consistency=ON
symbolic-links=0
[root@mysqlnode1 & 2 ~]# mysqld --user mysql --initialize
[root@mysqlnode1 & 2 ~]# /etc/init.d/mysqld start
[root@mysqlnode1 & 2 ~]# mysql_secure_installation
[root@mysqlnode1 & 2 ~]# mysql -p
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160', MASTER_USER='yu', MASTER_PASSWORD='123', MASTER_AUTO_POSITION=1;
Query OK, 0 rows affected, 2 warnings (0.00 sec)
mysql> start slave;
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.01 sec)
mysql> SET GLOBAL rpl_semi_sync_slave_enabled =1;
Query OK, 0 rows affected (0.00 sec)
mysql> STOP SLAVE IO_THREAD;
Query OK, 0 rows affected (0.00 sec)
mysql> START SLAVE IO_THREAD;
Query OK, 0 rows affected (0.00 sec)
mysql> SHOW STATUS LIKE 'Rpl_semi_sync%';
+----------------------------+-------+
| Variable_name | Value |
+----------------------------+-------+
| Rpl_semi_sync_slave_status | ON |
+----------------------------+-------+
1 row in set (0.01 sec)6.2.2安装MHA所需要的软件
#在MHA中
[root@mysql-mha ~]# unzip MHA-7.zip
[root@mysql-mha MHA-7]# yum install *.rpm -y
[root@mysql-mha MHA-7]# scp mha4mysql-node-0.58-0.el7.centos.noarch.rpm root@172.25.254.160:/mnt
[root@mysql-mha MHA-7]# scp mha4mysql-node-0.58-0.el7.centos.noarch.rpm root@172.25.254.170:/mnt
[root@mysql-mha MHA-7]# scp mha4mysql-node-0.58-0.el7.centos.noarch.rpm root@172.25.254.180:/mnt
#在sql-node中
[root@mysql ~]# yum install /mnt/mha4mysql-node-0.58-0.el7.centos.noarch.rpm -y
[root@mysqlnode1 ~]# yum install /mnt/mha4mysql-node-0.58-0.el7.centos.noarch.rpm -y
[root@mysqlnode2 ~]# yum install /mnt/mha4mysql-node-0.58-0.el7.centos.noarch.rpm -y在软件中包含的工具包介绍
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工具包 （通常由masterHA主机直接调用，无需人为执行）
save_binary_logs #保存和复制master的二进制日志
apply_diff_relay_logs #识别差异的中继日志事件并将其差异的事件应用于其他的slave
filter_mysqlbinlog #去除不必要的ROLLBACK事件（MHA已不再使用这个工具）
purge_relay_logs #清除中继日志（不会阻塞SQL线程）
6.2.3 配置MHA 的管理环境
1.生成配置目录和配置文件
[root@mysql-mha ~]# masterha_manager --help
Usage:
masterha_manager --global_conf=/etc/masterha_default.cnf #全局配置文件，记录公共设定
--conf=/usr/local/masterha/conf/app1.cnf #不同管理配置文件，记录各自配置
See online reference
(http://code.google.com/p/mysql-master-ha/wiki/masterha_manager) for details.因为我们当前只有一套主从，所以我们只需要写一个配置文件即可
rpm包中没有为我们准备配置文件的模板
可以解压源码包后在samples中找到配置文件的模板文件
#生成配置文件
[root@mysql-mha ~]# mkdir /etc/masterha
[root@mysql-mha MHA-7]# tar zxf mha4mysql-manager-0.58.tar.gz
[root@mysql-mha MHA-7]# cd mha4mysql-manager-0.58/samples/conf/
[root@mysql-mha conf]# cat masterha_default.cnf app1.cnf > /etc/masterha/app1.cnf
#编辑配置文件
[root@mysql-mha ~]# vim /etc/masterha/app1.cnf
[server default]
user=root #mysql管理员用户，因为需要做自动化配置
password=lee #mysql密码
ssh_user=root #ssh远程登陆用户
repl_user=repl #mysql主从复制中负责认证的用户
repl_password=lee #mysql主从复制中负责认证的用户密码
master_binlog_dir= /data/mysql #二进制日志目录
remote_workdir=/tmp #远程工作目录
#此参数使为了提供冗余检测，方式是mha主机网络自身的问题无法连接数据库节点，应为集群之外的主机
secondary_check_script= masterha_secondary_check -s 172.25.254.160 -s 172.25.254.11
ping_interval=3 #每隔3秒检测一次
#发生故障后调用的脚本，用来迁移vip
# master_ip_failover_script= /script/masterha/master_ip_failover
#电源管理脚本
# shutdown_script= /script/masterha/power_manager
#当发生故障后用此脚本发邮件或者告警通知
# report_script= /script/masterha/send_report
#在线切换时调用的vip迁移脚本，手动
# master_ip_online_change_script= /script/masterha/master_ip_online_change
manager_workdir=/etc/masterha #mha工作目录
manager_log=/var/etc/masterha/manager.log #mha日志
[server1]
hostname=172.25.254.160
candidate_master=1 #可能作为master的主机
check_repl_delay=0 #默认情况下如果一个slave落后master 100M的relay logs的话
#MHA将不会选择该slave作为一个新的master
#因为对于这个slave的恢复需要花费很长时间
#通过设置check_repl_delay=0
#MHA触发切换在选择一个新的master的时候将会忽略复制延时
#这个参数对于设置了candidate_master=1的主机非常有用
#因为这个候选主在切换的过程中一定是新的master
[server2]
hostname=172.25.254.170
candidate_master=1 #可能作为master的主机
check_repl_delay=0
[server3]
hostname=172.25.254.180
no_master=1 #不会作为master的主机2.检测配置：
a）检测网络及ssh免密
[root@mysql-mha ~]# masterha_check_ssh --conf=/etc/masterha/app1.cnf
Sat Aug 24 23:01:34 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Aug 24 23:01:34 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Aug 24 23:01:34 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Aug 24 23:01:34 2024 - [info] Starting SSH connection tests..
Sat Aug 24 23:01:36 2024 - [debug]
Sat Aug 24 23:01:35 2024 - [debug] Connecting via SSH from root@172.25.254.180(172.25.254.180:22) to root@172.25.254.160(172.25.254.160:22)..
Sat Aug 24 23:01:35 2024 - [debug] ok.
Sat Aug 24 23:01:35 2024 - [debug] Connecting via SSH from root@172.25.254.180(172.25.254.180:22) to root@172.25.254.170(172.25.254.170:22)..
Sat Aug 24 23:01:35 2024 - [debug] ok.
Sat Aug 24 23:01:45 2024 - [debug]
Sat Aug 24 23:01:34 2024 - [debug] Connecting via SSH from root@172.25.254.160(172.25.254.160:22) to root@172.25.254.170(172.25.254.170:22)..
Sat Aug 24 23:01:44 2024 - [debug] ok.
Sat Aug 24 23:01:44 2024 - [debug] Connecting via SSH from root@172.25.254.160(172.25.254.160:22) to root@172.25.254.180(172.25.254.180:22)..
Sat Aug 24 23:01:44 2024 - [debug] ok.
Sat Aug 24 23:01:45 2024 - [debug]
Sat Aug 24 23:01:34 2024 - [debug] Connecting via SSH from root@172.25.254.170(172.25.254.170:22) to root@172.25.254.160(172.25.254.160:22)..
Sat Aug 24 23:01:35 2024 - [debug] ok.
Sat Aug 24 23:01:35 2024 - [debug] Connecting via SSH from root@172.25.254.170(172.25.254.170:22) to root@172.25.254.180(172.25.254.180:22)..
Sat Aug 24 23:01:45 2024 - [debug] ok.
Sat Aug 24 23:01:45 2024 - [info] All SSH connection tests passed successfully.b）检测数据主从复制情况
#在数据节点master端
mysql> GRANT ALL ON *.* TO root@'%' identified by 'lee'; #允许root远程登陆
#执行检测
[root@mysql-mha ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf
Sat Aug 24 23:02:01 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sat Aug 24 23:02:01 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sat Aug 24 23:02:01 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sat Aug 24 23:02:01 2024 - [info] MHA::MasterMonitor version 0.58.
Sat Aug 24 23:02:02 2024 - [info] GTID failover mode = 1
Sat Aug 24 23:02:02 2024 - [info] Dead Servers:
Sat Aug 24 23:02:02 2024 - [info] Alive Servers:
Sat Aug 24 23:02:02 2024 - [info] 172.25.254.160(172.25.254.160:3306)
Sat Aug 24 23:02:02 2024 - [info] 172.25.254.170(172.25.254.170:3306)
Sat Aug 24 23:02:02 2024 - [info] 172.25.254.180(172.25.254.180:3306)
Sat Aug 24 23:02:02 2024 - [info] Alive Slaves:
Sat Aug 24 23:02:02 2024 - [info] 172.25.254.170(172.25.254.170:3306) Version=5.7.44-log (oldest major version between slaves) log-bin:enabled
Sat Aug 24 23:02:02 2024 - [info] GTID ON
Sat Aug 24 23:02:02 2024 - [info] Replicating from 172.25.254.160(172.25.254.160:3306)
Sat Aug 24 23:02:02 2024 - [info] Primary candidate for the new Master (candidate_master is set)
Sat Aug 24 23:02:02 2024 - [info] 172.25.254.180(172.25.254.180:3306) Version=5.7.44 (oldest major version between slaves) log-bin:disabled
Sat Aug 24 23:02:02 2024 - [info] GTID ON
Sat Aug 24 23:02:02 2024 - [info] Replicating from 172.25.254.160(172.25.254.160:3306)
Sat Aug 24 23:02:02 2024 - [info] Not candidate for the new Master (no_master is set)
Sat Aug 24 23:02:02 2024 - [info] Current Alive Master: 172.25.254.160(172.25.254.160:3306)
Sat Aug 24 23:02:02 2024 - [info] Checking slave configurations..
Sat Aug 24 23:02:02 2024 - [info] read_only=1 is not set on slave 172.25.254.170(172.25.254.170:3306).
Sat Aug 24 23:02:02 2024 - [info] read_only=1 is not set on slave 172.25.254.180(172.25.254.180:3306).
Sat Aug 24 23:02:02 2024 - [warning] log-bin is not set on slave 172.25.254.180(172.25.254.180:3306). This host cannot be a master.
Sat Aug 24 23:02:02 2024 - [info] Checking replication filtering settings..
Sat Aug 24 23:02:02 2024 - [info] binlog_do_db= , binlog_ignore_db=
Sat Aug 24 23:02:02 2024 - [info] Replication filtering check ok.
Sat Aug 24 23:02:02 2024 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Sat Aug 24 23:02:02 2024 - [info] Checking SSH publickey authentication settings on the current master..
Sat Aug 24 23:02:02 2024 - [info] HealthCheck: SSH to 172.25.254.160 is reachable.
Sat Aug 24 23:02:02 2024 - [info]
172.25.254.160(172.25.254.160:3306) (current master)
+--172.25.254.170(172.25.254.170:3306)
+--172.25.254.180(172.25.254.180:3306)
Sat Aug 24 23:02:02 2024 - [info] Checking replication health on 172.25.254.170..
Sat Aug 24 23:02:02 2024 - [info] ok.
Sat Aug 24 23:02:02 2024 - [info] Checking replication health on 172.25.254.180..
Sat Aug 24 23:02:02 2024 - [info] ok.
Sat Aug 24 23:02:02 2024 - [warning] master_ip_failover_script is not defined.
Sat Aug 24 23:02:02 2024 - [warning] shutdown_script is not defined.
Sat Aug 24 23:02:02 2024 - [info] Got exit code 0 (Not master dead).6.2.4 MHA的故障切换
MHA的故障切换过程
共包括以下的步骤：
1.配置文件检查阶段，这个阶段会检查整个集群配置文件配置
2.宕机的master处理，这个阶段包括虚拟ip摘除操作，主机关机操作
3.复制dead master和最新slave相差的relay log，并保存到MHA Manger具体的目录下
4.识别含有最新更新的slave
5.应用从master保存的二进制日志事件（binlog events）
6.提升一个slave为新的master进行复制
7.使其他的slave连接新的master进行复制
切换方式：
master未出现故障手动切换
#在master数据节点还在正常工作情况下
[root@mysql-mha ~]# masterha_master_switch \
--conf=/etc/masterha/app1.cnf \ #指定配置文件
--master_state=alive \ #指定master节点状态
--new_master_host=172.25.254.170 \ #指定新master节点
--new_master_port=3306 \ #执行新master节点端口
--orig_master_is_new_slave \ #原始master会变成新的slave
--running_updates_limit=10000 #切换的超时时间master故障手动切换
[root@mysqlnode2]# /etc/init.d/mysqld stop
[root@mysql-mha ~]# masterha_master_switch --master_state=dead --conf=/etc/masterha/app1.cnf --dead_master_host=172.25.254.170 --dead_master_port=3306 --new_master_host=172.25.254.160 --new_master_port=3306 --ignore_last_failover
--ignore_last_failover 表示忽略在/etc/masterha/目录中在切换过程中生成的锁文件恢复故障mysql节点
[root@mysqlnode2]# /etc/init.d/mysqld start
Starting MySQL. SUCCESS!
[root@mysqlnode2]# mysql -p
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160', MASTER_USER='yu', MASTER_PASSWORD='123', MASTER_AUTO_POSITION=1;
mysql> show slave status\G;
[root@mha ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf
Sun Aug 25 11:12:10 2024 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sun Aug 25 11:12:10 2024 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sun Aug 25 11:12:10 2024 - [info] Reading server configuration from /etc/masterha/app1.cnf..
Sun Aug 25 11:12:10 2024 - [info] MHA::MasterMonitor version 0.58.
Sun Aug 25 11:12:11 2024 - [info] GTID failover mode = 1
Sun Aug 25 11:12:11 2024 - [info] Dead Servers:
Sun Aug 25 11:12:11 2024 - [info] Alive Servers:
Sun Aug 25 11:12:11 2024 - [info] 172.25.254.160(172.25.254.160:3306)
Sun Aug 25 11:12:11 2024 - [info] 172.25.254.170(172.25.254.170:3306)
Sun Aug 25 11:12:11 2024 - [info] 172.25.254.180(172.25.254.180:3306)
Sun Aug 25 11:12:11 2024 - [info] Alive Slaves:
Sun Aug 25 11:12:11 2024 - [info] 172.25.254.170(172.25.254.170:3306) Version=5.7.44-log (oldest major version between slaves) log-bin:enabled
Sun Aug 25 11:12:11 2024 - [info] GTID ON
Sun Aug 25 11:12:11 2024 - [info] Replicating from 172.25.254.160(172.25.254.160:3306)
Sun Aug 25 11:12:11 2024 - [info] Primary candidate for the new Master (candidate_master is set)
Sun Aug 25 11:12:11 2024 - [info] 172.25.254.180(172.25.254.180:3306) Version=5.7.44 (oldest major version between slaves) log-bin:disabled
Sun Aug 25 11:12:11 2024 - [info] GTID ON
Sun Aug 25 11:12:11 2024 - [info] Replicating from 172.25.254.160(172.25.254.160:3306)
Sun Aug 25 11:12:11 2024 - [info] Not candidate for the new Master (no_master is set)
Sun Aug 25 11:12:11 2024 - [info] Current Alive Master: 172.25.254.160(172.25.254.160:3306)
Sun Aug 25 11:12:11 2024 - [info] Checking slave configurations..
Sun Aug 25 11:12:11 2024 - [info] read_only=1 is not set on slave 172.25.254.170(172.25.254.170:3306).
Sun Aug 25 11:12:11 2024 - [info] read_only=1 is not set on slave 172.25.254.180(172.25.254.180:3306).
Sun Aug 25 11:12:11 2024 - [warning] log-bin is not set on slave 172.25.254.180(172.25.254.180:3306). This host cannot be a master.
Sun Aug 25 11:12:11 2024 - [info] Checking replication filtering settings..
Sun Aug 25 11:12:11 2024 - [info] binlog_do_db= , binlog_ignore_db=
Sun Aug 25 11:12:11 2024 - [info] Replication filtering check ok.
Sun Aug 25 11:12:11 2024 - [info] GTID (with auto-pos) is supported. Skipping all SSH and Node package checking.
Sun Aug 25 11:12:11 2024 - [info] Checking SSH publickey authentication settings on the current master..
Sun Aug 25 11:12:11 2024 - [info] HealthCheck: SSH to 172.25.254.160 is reachable.
Sun Aug 25 11:12:11 2024 - [info]
172.25.254.160(172.25.254.160:3306) (current master)
+--172.25.254.170(172.25.254.170:3306)
+--172.25.254.180(172.25.254.180:3306)
Sun Aug 25 11:12:11 2024 - [info] Checking replication health on 172.25.254.170..
Sun Aug 25 11:12:11 2024 - [info] ok.
Sun Aug 25 11:12:11 2024 - [info] Checking replication health on 172.25.254.180..
Sun Aug 25 11:12:11 2024 - [info] ok.
Sun Aug 25 11:12:11 2024 - [warning] master_ip_failover_script is not defined.
Sun Aug 25 11:12:11 2024 - [warning] shutdown_script is not defined.
Sun Aug 25 11:12:11 2024 - [info] Got exit code 0 (Not master dead).自动切换
[root@mysql-mha masterha]# rm -fr app1.failover.complete #删掉切换锁文件
#监控程序通过指定配置文件监控master状态，当master出问题后自动切换并退出避免重复做故障切换
[root@mysql-mha masterha]# masterha_manager --conf=/etc/masterha/app1.cnf
[root@mysql-mha masterha]# cat /etc/masterha/manager.log
#恢复故障节点
[root@mysqlnode2 mysql]# /etc/init.d/mysqld start
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.160', MASTER_USER='yu', MASTER_PASSWORD='123', MASTER_AUTO_POSITION=1
#清除锁文件
[root@mysql-mha masterha]# rm -rf app1.failover.complete manager.log6.2.5 为MHA添加VIP功能
[root@mysql-mha ~]# ls
master_ip_failover master_ip_online_change MHA-7 MHA-7.zip
[root@mysql-mha ~]# cp master_ip_failover master_ip_online_change
/usr/local/bin/
[root@mysql-mha ~]# chmod +x /usr/local/bin/master_ip_*
#修改脚本在脚本中只需要修改下vip即可
[root@mysql-mha ~]# vim /usr/local/bin/master_ip_failover
my $vip = '172.25.254.100/24';
my $ssh_start_vip = "/sbin/ip addr add $vip dev eth0";
my $ssh_stop_vip = "/sbin/ip addr del $vip dev eth0";
[root@mysql-mha ~]# vim /usr/local/bin/master_ip_online_change
my $vip = '172.25.254.100/24';
my $ssh_start_vip = "/sbin/ip addr add $vip dev eth0";
my $ssh_stop_vip = "/sbin/ip addr del $vip dev eth0";
my $exit_code = 0;
[root@mysql-mha masterha]# masterha_manager --conf=/etc/masterha/app1.cnf & 启动监控程序
[root@mysql]# ip a a 172.25.254.100/24 dev eth0 #在master节点添加VIP模拟故障
[root@mysql ~]# /etc/init.d/mysqld stop #关闭主节点服务
[root@mysql-mha masterha]# cat manager.log恢复故障主机
[root@mysqlnode2]# /etc/init.d/mysqld start
mysql> CHANGE MASTER TO MASTER_HOST='172.25.254.10', MASTER_USER='repl',MASTER_PASSWORD='lee', MASTER_AUTO_POSITION=1
[root@mysql-mha masterha]# rm -rf app1.failover.complete manager.log手动切换后查看vip变化
[root@mysql-mha masterha]# masterha_master_switch --conf=/etc/masterha/app1.cnf
--master_state=alive --new_master_host=172.25.254.160 --new_master_port=3306 --orig_master_is_new_slave --running_updates_limit=10000
[root@mysql ~]# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> 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: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:61:a9:07 brd ff:ff:ff:ff:ff:ff
inet 172.25.254.160/24 brd 172.25.254.255 scope global noprefixroute eth0
valid_lft forever preferred_lft forever
inet 172.25.254.100/24 scope global secondary eth0
valid_lft forever preferred_lft forever
inet6 fe80::20c:29ff:fe61:a907/64 scope link 
2006
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
