Mysql 采用多线程进行复制是从 Mysql 5.6 开始支持的内容，但是 5.6 版本下有缺陷，虽然支持多线程，但是每个数据库只能一个线程，也就是说如果我们只有一个数据库，则主从复制时也只有一个线程在工作。相当于还是以前的单线程。 从 Mysql 5.7 开始支持同一数据库下并行主从复制。不过默认情况下，还是单数据库单个线程，如果需要使用多线程，需要在从节点进行配置。

Mysql 5.7 对主从复制增加了一种类型，共有两种类型，如下：

  • DATABASE 基于库的并行复制 ， 每个数据库对应一个复制线程
  • LOGICAL_CLOCK 基于组提交的并行复制方式，同一个数据库下可以有多个线程

下面的步骤，在从节点上进行配置。

查看当前配置

在开始配置之前，我们先看一下当前配置下的主从复制的进程数。

1
2
3
4
5
6
7
8
9
 
mysql> show processlist;
+----+-------------+-----------+------+---------+-------+--------------------------------------------------------+------------------+
| Id | User        | Host      | db   | Command | Time  | State                                                  | Info             |
+----+-------------+-----------+------+---------+-------+--------------------------------------------------------+------------------+
|  1 | system user |           | NULL | Connect | 91749 | Waiting for master to send event                       | NULL             |
|  2 | system user |           | NULL | Connect |   208 | Slave has read all relay log; waiting for more updates | NULL             |
| 37 | root        | localhost | NULL | Query   |     0 | starting                                               | show processlist |
+----+-------------+-----------+------+---------+-------+--------------------------------------------------------+------------------+
3 rows in set (0.00 sec)

从上面看出只有一个主进程在等待同步。

下面查看复制类型和并行数量配置

1
2
3
4
5
6
7
 
mysql> show variables like 'slave_parallel_type';
+---------------------+----------+
| Variable_name       | Value    |
+---------------------+----------+
| slave_parallel_type | DATABASE |
+---------------------+----------+
1 row in set (0.00 sec)

当前的复制类型是 DATABASE，也就是统一数据库下只有一个线程进行复制，不能并行复制。

1
2
3
4
5
6
7
 
mysql> show variables like 'slave_parallel_workers';
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| slave_parallel_workers | 0     |
+------------------------+-------+
1 row in set (0.01 sec)

当前并行工作的进程数是 0

配置多线程

1、停止从节点复制

1
2
 
mysql> stop slave;
Query OK, 0 rows affected (0.01 sec)

2、设置复制类型为 LOGICAL_CLOCK

1
2
3
4
5
6
7
8
9
10
 
mysql> set global slave_parallel_type='logical_clock';
Query OK, 0 rows affected (0.00 sec)

mysql> show variables like 'slave_parallel_type';
+---------------------+---------------+
| Variable_name       | Value         |
+---------------------+---------------+
| slave_parallel_type | LOGICAL_CLOCK |
+---------------------+---------------+
1 row in set (0.01 sec)

3、设置并行数量为 4

1
2
3
4
5
6
7
8
9
10
11
 
mysql> set global slave_parallel_workers=4;
Query OK, 0 rows affected (0.00 sec)

mysql> show variables like 'slave_parallel_workers';
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| slave_parallel_workers | 4     |
+------------------------+-------+
1 row in set (0.00 sec)

4、启动从节点复制

1
2
 
mysql> start slave;
Query OK, 0 rows affected (0.02 sec)

5、查看一下当前工作的线程数

1
2
3
4
5
6
7
8
9
10
11
12
13
 
mysql> show processlist;
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
| Id | User        | Host      | db   | Command | Time | State                                                  | Info             |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
| 37 | root        | localhost | NULL | Query   |    0 | starting                                               | show processlist |
| 38 | system user |           | NULL | Connect |    8 | Waiting for master to send event                       | NULL             |
| 39 | system user |           | NULL | Connect |    7 | Slave has read all relay log; waiting for more updates | NULL             |
| 40 | system user |           | NULL | Connect |    8 | Waiting for an event from Coordinator                  | NULL             |
| 41 | system user |           | NULL | Connect |    8 | Waiting for an event from Coordinator                  | NULL             |
| 42 | system user |           | NULL | Connect |    8 | Waiting for an event from Coordinator                  | NULL             |
| 43 | system user |           | NULL | Connect |    8 | Waiting for an event from Coordinator                  | NULL             |
+----+-------------+-----------+------+---------+------+--------------------------------------------------------+------------------+
7 rows in set (0.00 sec)

最后说一下为什么需要多线程复制？因为主从之间的同步会有延时，多线程的目的是为了尽量减少这个延时时间。虽然如何优化主从是一个系统的功能，不同的场景需要不同的解决方案，但是多线程至少从基础上能减少延迟时间。另外根据数据库的实际情况，能否真正减少延时，以及配置多少线程，则需要反复的测试得出适合自己的数据。

实例配置:

cat backup-my.cnf

# This MySQL options file was generated by innobackupex.

# The MySQL server

[mysqld]

port = 3310

#innodb_checksum_algorithm=innodb

#innodb_log_checksum_algorithm=innodb

innodb_data_file_path=ibdata1:200M:autoextend

innodb_log_files_in_group=2

innodb_log_file_size=1572864000

#innodb_fast_checksum=false

#innodb_page_size=16384

#innodb_log_block_size=512

innodb_undo_directory=.

innodb_undo_tablespaces=0

server-id = 1234

binlog-format = ROW

gtid-mode = ON

enforce-gtid-consistency = true

relay_log_recovery = 1

sync-binlog = 0

skip_slave_start = 1

slave-parallel-type=LOGICAL_CLOCK

slave-parallel-workers=32

master_info_repository=TABLE

relay_log_info_repository=TABLE

relay_log_recovery=ON

#rds_encrypt_data=false

#innodb_encrypt_algorithm=aes_128_ecb

　　

mysql> show processlist;

+----+-------------+-----------+------+---------+-------+----------------------------------------+------------------+

| Id | User        | Host      | db   | Command | Time  | State                                  | Info             |

+----+-------------+-----------+------+---------+-------+----------------------------------------+------------------+

|  2 | root        | localhost | NULL | Query   |     0 | starting                               | show processlist |

|  3 | system user |           | NULL | Connect |    13 | Queueing master event to the relay log | NULL             |

|  4 | system user |           | NULL | Connect |     0 | System lock                            | NULL             |

|  5 | system user |           | NULL | Connect | 49775 | Waiting for an event from Coordinator  | NULL             |

|  6 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

|  7 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

|  8 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

|  9 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 10 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 11 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 12 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 13 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 14 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 15 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 16 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 17 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 18 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 19 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 20 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 21 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 22 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 23 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 24 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 25 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 26 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 27 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 28 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 29 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 30 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 31 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 32 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 33 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 34 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 35 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

| 36 | system user |           | NULL | Connect |    13 | Waiting for an event from Coordinator  | NULL             |

+----+-------------+-----------+------+---------+-------+----------------------------------------+------------------+

35 rows in set (0.00 sec)

mysql> show global variables like 'slave_parallel_workers';

+------------------------+-------+

| Variable_name          | Value |

+------------------------+-------+

| slave_parallel_workers | 32    |

+------------------------+-------+

1 row in set (0.00 sec)

mysql> show global variables like '%slave_parallel_type%';

+---------------------+---------------+

| Variable_name       | Value         |

+---------------------+---------------+

| slave_parallel_type | LOGICAL_CLOCK |

+---------------------+---------------+

1 row in set (0.00 sec)

　　

Mysql 5.7 从节点配置多线程主从复制的更多相关文章

  1. Windows Server 2008R2配置MySQL Cluster并将管理节点和数据节点配置成windows服务

    说明:将mysql的管理节点和数据节点配置成windows服务是为了防止有人手误关闭管理节点或数据节点的dos命令窗口,管理节点或数据节点的命令窗口误关闭可能会造成mysql某台或某几台mysql不能 ...

  2. MySQL中双NDBD节点Cluster快速配置

    是MySQL适合于分布式计算环境的高实用.高冗余版本.它采用了NDB Cluster 存储引擎,允许在1个 Cluster 中运行多个MySQL服务器.在MyQL 5.0及以上的二进制版本中.以及与最 ...

  3. MySQL并发复制系列二：多线程复制

     http://blog.itpub.net/28218939/viewspace-1975822/ 并发复制(Parallel Replication) 系列二: Enhanced Multi-th ...

  4. MySQL并发复制系列二：多线程复制 2016

    并发复制(Parallel Replication) 系列二: Enhanced Multi-threaded Slaves作者:沃趣科技MySQL数据库工程师  麻鹏飞 首先梳理下传统MySQL/M ...

  5. MySQL集群（一）之主从复制

    前面学完了JDBC,接下来带大家感受一下MySQL集群!其实什么是MySQL集群?简单的说就是一群机器(服务器)的集合,它们连在一起来工作. 其实各种数据库都有自己的集群,常常的多: 我们要学习的就是 ...

  6. MySQL高可用之MHA配置

    本文简单介绍了MySQL的高可用实现方式之一的MHA MHA:Master High Availability,对主节点进行监控,可实现自动故障转移至其它从节点:通过提升某一从节点为新的主节点,基于主 ...

  7. Linux安装Mycat1.6.7.4并实现Mysql数据库读写分离简单配置

    1. Mycat简介 一个彻底开源的,面向企业应用开发的大数据库集群 支持事务.ACID.可以替代MySQL的加强版数据库 一个可以视为MySQL集群的企业级数据库,用来替代昂贵的Oracle集群 一 ...

  8. Docker安装mysql镜像并进行主从配置

    Docker安装mysql镜像并进行主从配置 1.下载需要的mysql版本镜像 docker pull mysql:5.6 2.启动mysql服务实例(基本启动) #启动主mysql docker r ...

  9. 数据库相关文章转载(1) MySQL性能优化之参数配置

    1.目的: 通过根据服务器目前状况,修改Mysql的系统参数,达到合理利用服务器现有资源,最大合理的提高MySQL性能. 2.服务器参数: 32G内存.4个CPU,每个CPU 8核. 3.MySQL目 ...

随机推荐

  1. [Linux] Systemd 入门教程：命令篇

    reference : http://www.ruanyifeng.com/blog/2016/03/systemd-tutorial-commands.html Systemd 是 Linux 系统 ...

  2. 【六】注入框架RoboGuice使用:(Singletons And ContextSingletons)

    上一篇我们简单的介绍了一下RoboGuice的使用([五]注入框架RoboGuice使用:(Your First POJO Injection)),今天我们来看下单例以及上下文单例(ContextSi ...

  3. Informatica 常用组件Lookup缓存之四 使用不高速缓存的查找或静态高速缓存

    默认情况下,在为高速缓存配置查找转换时,PowerCenter 将创建静态查找高速缓存.PowerCenter 将在处理第一个查找请求时创建高速缓存.它将根据查找条件为传递给转换的每行查询高速缓存.P ...

  4. java类过滤器，防止页面SQL注入

    package com.tarena.dingdang.filter; import java.io.IOException; import java.util.Enumeration; import ...

  5. javascript简单性能问题及学习笔记

    最近在看一本书:<高性能javaScript>,发现自己平时写js存在很多小细节上的问题,虽然这些问题不会导致程序运行出错,但是会导致界面加载变慢,用户体验变差,那么我们就来细细数一下应该 ...

  6. 五条强化 SSH 安全的建议

    当你查看你的 SSH 服务日志,可能你会发现充斥着一些不怀好意的尝试性登录.这里有 5 条常规建议(和一些个别特殊策略)可以让你的 OpenSSH 会话更加安全. 强化密码登录 密码登录很方便,因为你 ...

  7. mysql时间操作函数和存储过程

    因为业务须要统计一批数据.用到关于mysql的时间操作函数和存储过程,问题已经基本解决.把过程记录下: 1. mysql的语句中不支持直接用循环.循环仅仅能在存储过程中使用. 2. 写为文件时,注意一 ...

  8. [Backbone] Parse not formatted JSON code

    The good Dr. recently had another team implement the server and they slightly messed up the format o ...

  9. RPC框架研究（二）Hadoop源代码-1

    报名了阿里中间件性能大赛,我来说是一个全新的挑战.一切从空白学起,比赛的过程也是学习的过程 是的.想让自己学好.给自己报一个比赛吧~ 就像当初学围棋,也是报了围棋比赛,为了不至于输的太慘.一个星期里学 ...

  10. nGrinder对监控机器收集自定义数据及源码分析

    转载:https://blog.csdn.net/neven7/article/details/50782451 0.背景 性能测试工具nGrinder支持在无需修改源码的情况下,对目标服务器收集自定 ...