MySQL主从复制、读写分离
一、MySQL主从复制
1、作用
- 避免数据库的单点故障
- 实现多个MySQL间的数据一致
2、工作原理
- 核心依赖:二进制日志
1、主库将写操作记录到二进制日志
2、从库产生IO线程,连接主库,读取二进制日志内容,记录到本地的中继日志
3、从库产生SQL线程,读取中继日志的操作,在本地执行
存在问题:数据复制延迟,关注延迟时间
- 增加网络带宽
- 使用高IO的磁盘, SSD固态硬盘
3、常见架构
- 一主一从
- 一主多从
- 双主复制
二、主从复制配置
1、环境描述
192.168.140.10 主库
192.168.140.11 从库
2、关闭SELinux、时间同步
3、防火墙放行数据库服务
[root@zabbix_agent ~]# firewall-cmd --permanent --add-port=3306/tcp
success
[root@zabbix_agent ~]# firewall-cmd --reload
success
[root@zabbix_agent ~]#
4、主库配置
4.1 开启二进制日志
server_id=10
log_bin=/mysql/log/master
4.2 创建允许从库连接的复制用户
mysql> CREATE USER 'repluser'@"192.168.140.11" IDENTIFIED BY 'WWW.1.com';
Query OK, 0 rows affected (0.01 sec)
mysql> GRANT replication slave ON *.* TO 'repluser'@'192.168.140.11';
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
4.3 主库上进行数据备份,将备份文件拷贝到从库
[root@localhost ~]# mysqldump -uroot -pWWW.1.com --lock-all-tables --master-data=2 --all-databases > /opt/data.sql
[root@localhost ~]# scp /opt/data.sql root@192.168.140.11:/opt/
5、从库配置
5.1 安装MySQL
5.2 配置server_id、二进制日志
[root@zabbix_agent ~]# vim /etc/my.cnf
[mysqld]
server_id=11
log_bin=master
[root@zabbix_agent ~]# systemctl restart mysqld
5.3 恢复主库的备份
[root@zabbix_agent ~]# mysql -uroot -pWWW.1.com < /opt/data.sql
5.4 指定连接主库的信息
mysql> CHANGE MASTER TO
-> MASTER_HOST="192.168.140.10",
-> MASTER_USER="repluser",
-> MASTER_PASSWORD="WWW.1.com",
-> MASTER_LOG_FILE="master.000010",
-> MASTER_LOG_POS=781;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
5.5 启动复制线程
mysql> start slave;
Query OK, 0 rows affected (0.00 sec)
5.6 验证复制线程启动成功
mysql> show slave status\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.140.10
Master_User: repluser
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master.000010
Read_Master_Log_Pos: 1056
Relay_Log_File: zabbix_agent-relay-bin.000002
Relay_Log_Pos: 592
Relay_Master_Log_File: master.000010
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: 1056
Relay_Log_Space: 806
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: 5f753038-103a-11ef-994d-000c29cc6b2f
Master_Info_File: /var/lib/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)
Seconds_Behind_Master: 复制延迟时长,单位为秒
Read_Master_Log_Pos
Exec_Master_Log_Pos 通过这两个值的差,判断数据是否一致
在主库上查看连接的从库信息
mysql> show slave hosts;
+-----------+------+------+-----------+--------------------------------------+
| Server_id | Host | Port | Master_id | Slave_UUID |
+-----------+------+------+-----------+--------------------------------------+
| 11 | | 3306 | 10 | fc1c8e83-103b-11ef-992c-000c2929e543 |
+-----------+------+------+-----------+--------------------------------------+
1 row in set (0.00 sec)
三、读写分离
1、读写分离介绍
- 加快数据库工作效率
- 在主从复制环境 ,主库执行写操作,从库执行读操作
2、实现方案
- 开发在业务代码中固定写数据库地址
- 数据库中间件
mysql-proxy MySQL官方
aomerba 阿里,开源
MyCAT 国内,开源
Atlas 360
四、MyCAT实现读写分离
1、mycat软件安装
1.1 安装JDK 1.8
[root@localhost ~]# tar xf jdk-8u91-linux-x64.tar.gz -C /usr/local/
[root@localhost ~]# ls /usr/local/
bin etc games include jdk1.8.0_91 lib lib64 libexec sbin share src
1.2 为JDK添加环境变量
[root@localhost ~]# vim /etc/profile
export JAVA_HOME=/usr/local/jdk1.8.0_91
export PATH=$PATH:$JAVA_HOME/bin
[root@localhost ~]# source /etc/profile
[root@localhost ~]# java -version
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)
1.3 安装mycat
[root@localhost ~]# tar xf Mycat-server-1.6-RELEASE-20161028204710-linux.tar.gz -C /usr/local/
[root@localhost ~]# ls /usr/local/
bin etc games include jdk1.8.0_91 lib lib64 libexec mycat sbin share src
[root@localhost ~]# vim /etc/profile
export MYCAT_HOME=/usr/local/mycat
[root@localhost ~]# source /etc/profile
2、编辑schema.xml文件,定义读写分离
[root@localhost ~]# cat /usr/local/mycat/conf/schema.xml
<?xml version="1.0"?>
<!DOCTYPE mycat:schema SYSTEM "schema.dtd">
<mycat:schema xmlns:mycat="http://io.mycat/">
// 定义虚拟数据库,关联dataNode
<schema name="game" checkSQLschema="false" sqlMaxLimit="100" dataNode="dn01">
</schema>
// 定义真实数据库,关联dataHost
<dataNode name="dn01" dataHost="dh01" database="game" />
// 定义数据主机,主库、从库地址
<dataHost name="dh01" maxCon="1000" minCon="10" balance="1"
writeType="0" dbType="mysql" dbDriver="native" switchType="1" slaveThreshold="100">
<heartbeat>select user()</heartbeat>
<!-- can have multi write hosts -->
<writeHost host="hostM1" url="192.168.140.10:3306" user="mycatuser"
password="WWW.1.com">
</writeHost>
<writeHost host="hostS1" url="192.168.140.11:3306" user="mycatuser"
password="WWW.1.com" />
</dataHost>
</mycat:schema>
3、在后端数据库建立允许mycat连接的用户
mysql> CREATE USER 'mycatuser'@"192.168.140.12" IDENTIFIED BY 'WWW.1.com';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT all ON game.* TO 'mycatuser'@"192.168.140.12";
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
4、在MyCAT上创建允许业务连接的用户
[root@localhost conf]# vim /usr/local/mycat/conf/server.xml
<user name="admin">
<property name="password">123456</property>
<property name="schemas">game</property>
</user>
5、启动MyCAT
[root@localhost ~]# /usr/local/mycat/bin/mycat start
Starting Mycat-server...
[root@localhost ~]# netstat -tunlp | grep java
tcp 0 0 127.0.0.1:32000 0.0.0.0:* LISTEN 1765/java
tcp6 0 0 :::1984 :::* LISTEN 1765/java
tcp6 0 0 :::8066 :::* LISTEN 1765/java
tcp6 0 0 :::9066 :::* LISTEN 1765/java
6、测试读写分离
6.1 连接Mycat进行写操作
连接Mycat执行写操作,到后端从库上验证有同步的数据
6.2 测试读操作
五、主从复制维护
1、从库宕机恢复后,会自动连接主库复制数据
- master.info
- relay-log.info
- 文件中记录着连接主库的地址信息、二进制日志、中继日志信息
2、模拟主从复制故障
2.1 IO线程故障
网络通信 ping、traceroute
主库服务宕机/防火墙拦截 telnet
用户密码有错误、用户授权replication slave
2.2 SQL线程故障
- 从库上执行了写操作,引起数据冲突
从库设置为只读
# vim /etc/my.cnf
[mysqld]
read_only=1
3、主从角色切换
3.1 将从服务器提升为新主
关闭复制线程 sql> stop slave;
清除主服务器的连接信息 sql> reset slave all;
删除read_only只读配置
3.2 将业务的数据库连接 切换到新主服务器
[root@localhost ~]# vim 网页目录/config/config_global.php
// ---------------------------- CONFIG DB ----------------------------- //
$_config['db'][1]['dbhost'] = '192.168.140.11';
$_config['db'][1]['dbuser'] = 'dzuser';
$_config['db'][1]['dbpw'] = 'WWW.1.com';
$_config['db'][1]['dbcharset'] = 'utf8mb4';
$_config['db'][1]['pconnect'] = 0;
$_config['db'][1]['dbname'] = 'discuz';
mysql> CREATE USER 'dzuser'@"%" IDENTIFIED BY 'WWW.1.com';
Query OK, 0 rows affected (0.00 sec)
mysql> GRANT all ON discuz.* TO 'dzuser'@"%";
Query OK, 0 rows affected (0.00 sec)
mysql> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)
3.3 将故障的主机修复完毕后,作为从连接到新主上
六、基于GTID的主从复制
1、GTID的介绍
GTID, 全局事务ID, 数据库中的每个事务/操作都有一个惟一ID, 从库连接主库复制数据时,会根据GTID自动识别哪些操作执行过,哪些操作没有执行
MySQL 5.6版本以上支持的
- GTID == server_UUID + 数字编号
2、基于GTID的主从复制
2.1 清理MySQL现有所有数据
2.2 开启GTID的功能
[root@localhost ~]# vim /etc/my.cnf
gtid_mode=ON // 启用gtid
enforce_gtid_consistency=true //强制gtid的一致性
2.3 从库连接主库
mysql> CHANGE MASTER TO
-> MASTER_HOST="192.168.140.10",
-> MASTER_USER="repluser",
-> MASTER_PASSWORD="WWW.1.com",
-> MASTER_AUTO_POSITION=1;
Query OK, 0 rows affected, 2 warnings (0.02 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.140.10
Master_User: repluser
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master.000002
Read_Master_Log_Pos: 1177
Relay_Log_File: zabbix_agent-relay-bin.000002
Relay_Log_Pos: 1384
Relay_Master_Log_File: master.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: 1177
Relay_Log_Space: 1598
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: 997e5ca7-1294-11ef-9338-000c29cc6b2f
Master_Info_File: /var/lib/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: 997e5ca7-1294-11ef-9338-000c29cc6b2f:1-5
Executed_Gtid_Set: 997e5ca7-1294-11ef-9338-000c29cc6b2f:1-5,
c992938f-1294-11ef-93fe-000c2929e543:1-2
Auto_Position: 1
Replicate_Rewrite_DB:
Channel_Name:
Master_TLS_Version:
1 row in set (0.00 sec)
七、双主复制
- 在旧主服务器建立允许远程连接的用户
双主复制都允许执行写操作,同时会复制给对方,为了避免由于主键冲突导致故障,可以调整自动增长的步长
# vim /etc/my.cnf
auto_increment_offset=2 // 定义起始数字
auto_increment_increment=2 // 定义步长