MySQL Group Replication 搭建[Single-Primary Mode]

最新推荐文章于 2024-02-21 20:13:59 发布
最新推荐文章于 2024-02-21 20:13:59 发布
阅读量4.7k 收藏 3
点赞数 1
分类专栏： mysql 文章标签： mysql 高可用
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/d6619309/article/details/53786995
版权

这篇文章记录如何部署mysql group replication 单写模式 (single-primary mode)

部署方式大致与多写模式的部署一致，所需要修改的只有my.cnf里面关于group replication的配置。

多写模式的部署参考另外一篇文章:

http://blog.csdn.net/d6619309/article/details/53691790

1. 环境准备

  • CentOS5.6
  • mysql-5.7.17-linux-glibc2.5-x86_64.tar.gz

2. 部署

我们的目标是在一台机器上安装3个mysql实例，然后配置mysql group replication，模式为single-primary mode

安装目录说明如下:

1) 实例数据将安装在

  • s1: /dba/mysql/data/s1
  • s2: /dba/mysql/data/s2
  • s3: /dba/mysql/data/s3

2) mysql5.7解压到

/dba/mysql/mysql-5.7

2.1 安装多实例(s1、s2、s3)

出于试验和测试的考虑，我们直接用编译好的mysql安装包进行精简安装:

cd /dba/mysql
mkdir data
mysql-5.7/bin/mysqld --initialize-insecure --basedir=$PWD/mysql-5.7 --datadir=$PWD/data/s1
mysql-5.7/bin/mysqld --initialize-insecure --basedir=$PWD/mysql-5.7 --datadir=$PWD/data/s2
mysql-5.7/bin/mysqld --initialize-insecure --basedir=$PWD/mysql-5.7 --datadir=$PWD/data/s3

2.2 s1实例部署

2.2.1 配置实例

cd $PWD/data/s1
touch s1.cnf
vi s1.cnf
  • 加入主配置
[mysqld]

# server configuration
datadir=/dba/mysql/data/s1
basedir=/dba/mysql/mysql-5.7/

port=24801
socket=/dba/mysql/data/s1/s1.sock
  • 加入replication配置
server_id=1
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

其中大部分配置是为了打开group replication必须配置的，详见:

http://mysqlhighavailability.com/mysqlha/gr/doc/limitations.html

  • 加入group replication配置
transaction_write_set_extraction=XXHASH64
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
loose-group_replication_start_on_boot=off
loose-group_replication_local_address= "127.0.0.1:24901"
loose-group_replication_group_seeds= "127.0.0.1:24901,127.0.0.1:24902,127.0.0.1:24903"
loose-group_replication_bootstrap_group= off
loose-group_replication_single_primary_mode=true
loose-group_replication_enforce_update_everywhere_checks=false

配置解释见:

http://mysqlhighavailability.com/mysqlha/gr/doc/getting_started.html#group-replication

注意关闭多写模式相关配置:

  • loose-group_replication_single_primary_mode=true
  • loose-group_replication_enforce_update_everywhere_checks=false

2.2.2 启动实例

执行以下命令启动s1实例:

nohup mysql-5.7/bin/mysqld --defaults-file=data/s1/s1.cnf >data/s1/nohup.out 2>data/s1/nohup.out &

注意mysql用户必须拥有对data目录下的读写权限

2.2.3 用户授权

成功启动之后，登陆mysql:

mysql -uroot -h127.0.0.1 -P24801 --skip-password

登陆之后建议修改root登陆密码，通过以下语句修改:

SET SQL_LOG_BIN=0;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'mysql';
SET SQL_LOG_BIN=1;

修改密码遇到ERROR：

ERROR 1819 (HY000): Your password does not satisfy the current policy requirements

密码安全策略太高引起，参考http://www.cnblogs.com/ivictor/p/5142809.html

执行：

set global validate_password_policy=0;

然后再设置密码即可

mysql命令行下创建group replication所需要的用户:

SET SQL_LOG_BIN=0;
CREATE USER rpl_user@'%';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%' IDENTIFIED BY 'rpl_pass';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;
CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='rpl_pass' FOR CHANNEL 'group_replication_recovery';

2.2.4 开启组复制

mysql命令行下执行:

mysql> INSTALL PLUGIN group_replication SONAME 'group_replication.so';
mysql> SHOW PLUGINS;
+----------------------------+----------+--------------------+----------------------+-------------+
| Name                       | Status   | Type               | Library              | License     |
+----------------------------+----------+--------------------+----------------------+-------------+
| binlog                     | ACTIVE   | STORAGE ENGINE     | NULL                 | PROPRIETARY |

(...)

| group_replication          | ACTIVE   | GROUP REPLICATION  | group_replication.so | PROPRIETARY |
+----------------------------+----------+--------------------+----------------------+-------------+

看到group_replication确保安装插件成功

接下来执行下面的语句，启动group replication:

SET GLOBAL group_replication_bootstrap_group=ON;
START GROUP_REPLICATION;
SET GLOBAL group_replication_bootstrap_group=OFF;

执行下面的语句，验证group replication已经成功启动:

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 3c992270-c282-11e6-93bf-fa163ee40410 | ${yourhostname}  |       24801 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
1 row in set (0.00 sec)

接下来创建测试用的库和表:

mysql> CREATE DATABASE test;
Query OK, 1 row affected (0,00 sec)

mysql> use test
Database changed
mysql> CREATE TABLE t1 (c1 INT PRIMARY KEY, c2 TEXT NOT NULL);
Query OK, 0 rows affected (0,00 sec)

mysql> INSERT INTO t1 VALUES (1, 'Luis');
Query OK, 1 row affected (0,01 sec)

mysql> SELECT * FROM t1;
+----+------+
| c1 | c2   |
+----+------+
|  1 | Luis |
+----+------+
1 row in set (0,00 sec)

mysql> show binlog events;
+---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+
| Log_name      | Pos  | Event_type     | Server_id | End_log_pos | Info                                                                                                                 |
+---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+
| binlog.000001 |    4 | Format_desc    |         1 |         123 | Server ver: 5.7.17-log, Binlog ver: 4                                                                                |
| binlog.000001 |  123 | Previous_gtids |         1 |         150 |                                                                                                                      |
| binlog.000001 |  150 | Gtid           |         1 |         211 | SET @@SESSION.GTID_NEXT= '3c992270-c282-11e6-93bf-fa163ee40410:1'                                                    |
| binlog.000001 |  211 | Query          |         1 |         386 | ALTER USER 'root'@'localhost' IDENTIFIED WITH 'mysql_native_password' AS '*E74858DB86EBA20BC33D0AECAE8A8108C56B17FA' |
| binlog.000001 |  386 | Gtid           |         1 |         447 | SET @@SESSION.GTID_NEXT= 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1'                                                    |
| binlog.000001 |  447 | Query          |         1 |         506 | BEGIN                                                                                                                |
| binlog.000001 |  506 | View_change    |         1 |         645 | view_id=14817781596395401:1                                                                                          |
| binlog.000001 |  645 | Query          |         1 |         710 | COMMIT                                                                                                               |
| binlog.000001 |  710 | Gtid           |         1 |         771 | SET @@SESSION.GTID_NEXT= 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:2'                                                    |
| binlog.000001 |  771 | Query          |         1 |         861 | CREATE DATABASE test                                                                                                 |
| binlog.000001 |  861 | Gtid           |         1 |         922 | SET @@SESSION.GTID_NEXT= 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:3'                                                    |
| binlog.000001 |  922 | Query          |         1 |        1046 | use `test`; CREATE TABLE t1 (c1 INT PRIMARY KEY, c2 TEXT NOT NULL)                                                   |
| binlog.000001 | 1046 | Gtid           |         1 |        1107 | SET @@SESSION.GTID_NEXT= 'aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:4'                                                    |
| binlog.000001 | 1107 | Query          |         1 |        1175 | BEGIN                                                                                                                |
| binlog.000001 | 1175 | Table_map      |         1 |        1218 | table_id: 219 (test.t1)                                                                                              |
| binlog.000001 | 1218 | Write_rows     |         1 |        1260 | table_id: 219 flags: STMT_END_F                                                                                      |
| binlog.000001 | 1260 | Xid            |         1 |        1287 | COMMIT /* xid=47 */                                                                                                  |
+---------------+------+----------------+-----------+-------------+----------------------------------------------------------------------------------------------------------------------+
17 rows in set (0.00 sec)

2.3 增加新成员s2

cd data/s2
touch s2.cnf
vi s2.cnf

与配置s1实例类似，增加s2.cnf并写入如下配置:

[mysqld]

# server configuration
datadir=/dba/mysql/data/s2
basedir=/dba/mysql/mysql-5.7/

port=24802
socket=/dba/mysql/data/s2/s2.sock

#
# Replication configuration parameters
#
server_id=2
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

#
# Group Replication configuration
#
transaction_write_set_extraction=XXHASH64
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
loose-group_replication_start_on_boot=off
loose-group_replication_local_address= "127.0.0.1:24902"
loose-group_replication_group_seeds= "127.0.0.1:24901,127.0.0.1:24902,127.0.0.1:24903"
loose-group_replication_bootstrap_group= off
loose-group_replication_single_primary_mode=true
loose-group_replication_enforce_update_everywhere_checks=false

之后启动s2实例:

nohup mysql-5.7/bin/mysqld --defaults-file=data/s2/s2.cnf >data/s2/nohup.out 2>data/s2/nohup.out &

修改用户密码:

SET SQL_LOG_BIN=0;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'mysql';
SET SQL_LOG_BIN=1;

之后配置group replication需要的用户:

SET SQL_LOG_BIN=0;
CREATE USER rpl_user@'%';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%' IDENTIFIED BY 'rpl_pass';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;
CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='rpl_pass' FOR CHANNEL 'group_replication_recovery';

接下来安装group replication插件:

mysql> INSTALL PLUGIN group_replication SONAME 'group_replication.so';

然后就可以把s2添加到当前group里面:

mysql> START GROUP_REPLICATION;

【注意】 前面的用户密码修改和创建用户操作必须设置binlog不记录，执行后再打开，否则会引起START GROUP_REPLICATION执行报错:

报错信息如下所示:

ERROR 3092 (HY000): The server is not configured properly to be an active member of the group. Please see more details on error log.

mysql后台报错信息:

2016-12-15T07:51:28.317816Z 0 [ERROR] Plugin group_replication reported: 'This member has more executed transactions than those present in the group. Local transactions: f16f7f74-c283-11e6-ae37-fa163ee40410:1 > Group transactions: 3c992270-c282-11e6-93bf-fa163ee40410:1,
aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa:1-5'
2016-12-15T07:51:28.317878Z 0 [ERROR] Plugin group_replication reported: 'The member contains transactions not present in the group. The member will now exit the group.'
2016-12-15T07:51:28.317887Z 0 [Note] Plugin group_replication reported: 'To force this member into the group you can use the group_replication_allow_local_disjoint_gtids_join option'
2016-12-15T07:51:28.317999Z 14 [Note] Plugin group_replication reported: 'Going to wait for view modification'
2016-12-15T07:51:28.318429Z 0 [Note] Plugin group_replication reported: 'getstart group_id 4317e324'
2016-12-15T07:51:32.437462Z 0 [Note] Plugin group_replication reported: 'state 4330 action xa_terminate'
2016-12-15T07:51:32.437897Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2016-12-15T07:51:32.437913Z 0 [Note] Plugin group_replication reported: 'state 4257 action xa_exit'
2016-12-15T07:51:32.437981Z 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
2016-12-15T07:51:32.437993Z 0 [Note] Plugin group_replication reported: 'new state x_start'
2016-12-15T07:51:37.472364Z 14 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
2016-12-15T07:51:37.472474Z 14 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
2016-12-15T07:51:37.472943Z 19 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2016-12-15T07:51:37.485851Z 16 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'

如果出现上述问题，解决方案是：根据提示打开group_replication_allow_local_disjoint_gtids_join选项，mysql命令行执行:

mysql> set global group_replication_allow_local_disjoint_gtids_join=ON;

然后再执行:

mysql> start group_replication;
Query OK, 0 rows affected (7.89 sec)

执行成功，查询组成员信息:

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 3c992270-c282-11e6-93bf-fa163ee40410 | ${yourhostname}  |       24801 | ONLINE       |
| group_replication_applier | f16f7f74-c283-11e6-ae37-fa163ee40410 | ${yourhostname}  |       24802 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
2 rows in set (0.00 sec)

看到实例s2已经加入当前group

查看database发现test数据库和表t1已经被同步创建:

mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| test               |
+--------------------+
5 rows in set (0.00 sec)

mysql> use test;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
+----------------+
1 row in set (0.00 sec)

表t1的数据也被同步了:

mysql> select * from t1;
+----+------+
| c1 | c2   |
+----+------+
|  1 | Luis |
+----+------+
1 row in set (0.00 sec

2.4 增加新实例s3

与增加s2实例类似，不赘述，直接看配置:

cd data/s3
touch s3.cnf
vi s3.cnf
[mysqld]

# server configuration
datadir=/dba/mysql/data/s3
basedir=/dba/mysql/mysql-5.7/

port=24803
socket=/dba/mysql/data/s3/s3.sock

#
# Replication configuration parameters
#
server_id=3
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

#
# Group Replication configuration
#
transaction_write_set_extraction=XXHASH64
loose-group_replication_group_name="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa"
loose-group_replication_start_on_boot=off
loose-group_replication_local_address= "127.0.0.1:24903"
loose-group_replication_group_seeds= "127.0.0.1:24901,127.0.0.1:24902,127.0.0.1:24903"
loose-group_replication_bootstrap_group= off
loose-group_replication_single_primary_mode=true
loose-group_replication_enforce_update_everywhere_checks=false

启动s3实例:

nohup mysql-5.7/bin/mysqld --defaults-file=data/s3/s3.cnf >data/s3/nohup.out 2>data/s3/nohup.out &

登陆、修改密码后，执行:

SET SQL_LOG_BIN=0;
ALTER USER 'root'@'localhost' IDENTIFIED BY 'mysql';
SET SQL_LOG_BIN=1;
SET SQL_LOG_BIN=0;
CREATE USER rpl_user@'%';
GRANT REPLICATION SLAVE ON *.* TO rpl_user@'%' IDENTIFIED BY 'rpl_pass';
FLUSH PRIVILEGES;
SET SQL_LOG_BIN=1;
CHANGE MASTER TO MASTER_USER='rpl_user', MASTER_PASSWORD='rpl_pass' FOR CHANNEL 'group_replication_recovery';

安装插件:

INSTALL PLUGIN group_replication SONAME 'group_replication.so';

最后将s3加入group:

START GROUP_REPLICATION;

查看同步状态:

mysql> SELECT * FROM performance_schema.replication_group_members;
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| CHANNEL_NAME              | MEMBER_ID                            | MEMBER_HOST | MEMBER_PORT | MEMBER_STATE |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
| group_replication_applier | 3c992270-c282-11e6-93bf-fa163ee40410 | ${yourhost}  |       24801 | ONLINE       |
| group_replication_applier | f16f7f74-c283-11e6-ae37-fa163ee40410 | ${yourhost}  |       24802 | ONLINE       |
| group_replication_applier | f9b49bd8-c283-11e6-afb2-fa163ee40410 | ${yourhost}  |       24803 | ONLINE       |
+---------------------------+--------------------------------------+-------------+-------------+--------------+
3 rows in set (0.00 sec)


mysql> show databases;
+--------------------+
| Database           |
+--------------------+
| information_schema |
| mysql              |
| performance_schema |
| sys                |
| test               |
+--------------------+
5 rows in set (0.00 sec)

mysql> use test;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show tables;
+----------------+
| Tables_in_test |
+----------------+
| t1             |
+----------------+
1 row in set (0.00 sec)

mysql> select * from t1;
+----+------+
| c1 | c2   |
+----+------+
|  1 | Luis |
+----+------+
1 row in set (0.00 sec)

这个时候已经完成了一个group replication multi primary mode的部署了。

如何查看group内哪个节点是作为primary节点，官方提供了一个方法:

SELECT VARIABLE_VALUE FROM performance_schema.global_status WHERE VARIABLE_NAME= 'group_replication_primary_member';

得到的是primary节点的MEMBER_ID，这个id等价于server_uuid

3. 简单测试

  • 在s3上面执行:
mysql> insert into t1(c1, c2) values(null, 's3');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement

执行报错，single-primary mode下只有primary可以写(s1)。

  • 在s2上面执行:
mysql> insert into t1(c1, c2) values(null, 's2');
ERROR 1290 (HY000): The MySQL server is running with the --super-read-only option so it cannot execute this statement

同样报错。

  • 在s1上面执行:
mysql> insert into t1(c1, c2) values(null, 's1');
Query OK, 1 row affected (0.03 sec)

执行成功。

在s2和s3上查询数据同步情况:

mysql> select * from t1;
+----+------+
| c1 | c2   |
+----+------+
|  1 | Luis |
|  8 | s1   |
+----+------+
2 rows in set (0.00 sec)

group replication 自增列的步长默认为7

4. 参考

http://dev.mysql.com/doc/refman/5.7/en/group-replication-getting-started.html

ZzzCrazyPig
关注
  • 1
    点赞
  • 踩
  • 3
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
MySQL Group Replication 详细搭建部署过程
12-28
MySQL Group Replication 详细搭建部署过程
Mysql Group Replication搭建
Du.的博客
03-29 750
1. MGR介绍 Group Replication is a built-in MySQL plugin provided with MySQL Server 5.7.17 and later. MGR利用的是mysql（社区版或商用版）5.7.17后内置的group_replication的插件实现的，有单主多从模式和多主模式，oracle官方推荐单主多从模式，实现读写分离 由若干个节点（最多9个）共同组成一个复制组，一个事务的提交，必须经过组内大多数节点（N / 2 + 1）决议并通过，才...
【MySQL高可用集群】MySQL的MGR搭建
最新发布
天涯的浪子
02-21 1226
如果属性 group_replication_single_primary_mode =ON，则其他后启动组复制服务的节点会以slave 节点的身份自动加入复制组 ，最终组成一主多从集群。属性 group_replication_bootstrap_group 配置是否引导组复制，如果某个节点设置此属性为ON，则先启动此节点创建一个组服务并成为 master 节点，接受其他后启动节点加入组复制集群。10.53.207.20 作为引导节点启动组复制服务，此节点将作为主节点接收其他节点加入集群。
组复制安装部署 | 全方位认识 MySQL 8.0 Group Replication
老叶茶馆
08-20 1047
作者 罗小波 · 数据库技术专家出品 沃趣科技组复制以插件的形式提供给MySQL Server使用，组中的每个Server都需要配置和安装MGR插件。本节将以三节点的组复制为例，详细...
MySQL 组复制Group Replication安装
jolly10的专栏
05-16 665
1.安装环境说明 ：机器名        IP                        角色qht131    172.17.61.131        primary   qht132    172.17.61.132        secdnode1qht132    172.17.61.133        secdnode2用三台机器组成mysql group replication...
mysql group replication 单写模式 (single-primary mode) 搭建
lvfk
11-15 1195
一、环境配置 节点信息 servername ip port group port mgr_one 10.168.1.227 3306 6606 mgr_two 10.168.1.226 3306 6606 mgr_three 10.168.1.228 3306 6606 group 同步用户和密码 用户：rpl_lvfk 密码：rpl_lvfk 系统：Ubunt
MySQL高可用之组复制技术(3)：配置多主模型的组复制
weixin_34121304的博客
06-22 121
MySQL组复制系列文章： MySQL组复制大纲 MySQL组复制(1)：组复制技术简介 MySQL组复制(2)：配置单主模型的组复制 MySQL组复制(3)：配置多主模型的组复制 MySQL组复制(4)：组复制理论透彻分析 在这一篇，我演示的是如何配置MySQL组复制的多主模型(multi-primary)。在配置上，多主模型的组复制和单主模型基本没区别。 本文仅为搭建和维护多主模...
mysql mgr 单主模式_Mysql MGR单主模式的简单配置
weixin_31146939的博客
01-19 718
[MGR简介]基于传统异步复制和半同步复制的缺陷——数据的一致性问题无法保证，MySQL官方在5.7.17版本正式推出组复制(MySQLGroupReplication，简称MGR)，以插件形式提供，实现了分布式下数据的最终一致性,提供了高可用、高扩展、高可靠的MySQL集群服务。[同步原理]MGR是一种可用于实现容错系统的技术。复制组是一个通过消息传递相互交互的Server集群，由多个Serve...
Mysql Group Replication in Single-Primary Mode安装部署配置
weixin_34417200的博客
10-12 126
背景： MySQL组复制作为一个插件提供给MySQL服务器，组中的每个服务器都需要配置和安装插件，本节提供了一个详细的教程，其中包含了创建一个至少有三个服务器的复制组所需的步骤，组中的每个服务器实例都可以在独立的物理机器上运行，也可以在同一台机器上运行，本次介绍Single-Primary Mode的安装部署（在单主模式下，只有一个节点可以对外提供...
MySQL并行复制的深入浅出
yaowen_08的博客
06-06 500
并行复制的背景 首先，为什么会有并行复制这个概念呢？ 1.DBA都应该知道，MySQL的复制是基于binlog的。 2.MySQL复制包括两部分，IO线程 和 SQL线程。 3.IO线程主要是用于拉取接收Master传递过来的binlog，并将其写入到relay log 4.SQL线程主要负责解析relay log，并应用到slave中 5.不管怎么说，IO和SQL线程都是单线程的，然后master却是多线程的，所以难免会有延迟，为了解决这个问题，多线程应运而生了。 6.IO多线程？ 6.1 I
MySQL5.7 MGR 集群搭建
热门推荐
高飞的博客
06-16 12万+
mysql mgr 集群
MySQL Group Replication-MGR切换工具
12-15
MySQL Group Replication（MGR）组复制是MySQL官方在5.7.17版本引进的一个数据库高可用与高扩展的解决方案，以插件形式提供，实现了分布式下数据的最终一致性。但是官方没有给出vip的漂移方案，官方的推荐是使用...
mysql-group-replication-docker:使用Docker MySQL映像设置组复制
05-22
全文参考使用Docker容器设置组复制的其他方法 先决条件安装了Docker概述我们首先从Docker Hub（ ）中拉出mysql 8 ，然后将创建一个名为group1的Docker网络，最后使用4创建一个Group Replication拓扑。不同主机中的组...
MySQL Group Replication环境搭建实战手册
09-16
MySQL Group Replication环境搭建实战手册
python-mysql-replication：纯Python实现MySQL复制协议的基础是PyMYSQL
02-03
用例MySQL到NoSQL数据库复制MySQL到搜索引擎复制数据库中的某些更改使缓存无效审计实时分析文献资料正在进行中的文档可在以下位置找到： ： 有关构建文档的说明，请参见： ： 安装pip install mysql-replication邮件...
MySQL Group Replication 介绍
CrazyPig的技术博客
12-16 2万+
2016-12-12，一个重要的日子，mysql5.7.17 GA版发布，正式发布了Group Replication(组复制) Plugin，增强了mysql原有的高可用方案(原有的高可用方案是指mysql主从架构)，提供了重要的特性——多写，保证组内高可用，数据强一致性。
MySQL Group Replication HA with ProxySQL [主节点故障切换对应用无感知]
CrazyPig的技术博客
01-18 1万+
MGR单主模式下，实现主节点故障切换，对应用无感知
mysql lock in share mode 和 select for update
CrazyPig的技术博客
09-28 1万+
这两个语句是在事务内起作用的，所涉及的概念是行锁。它们能够保证当前session事务所锁定的行不会被其他session所修改
MySQL Group Replication 搭建[Multi-Primary Mode]
CrazyPig的技术博客
12-16 9293
这篇文章记录如何部署mysql group replication 多写模式 (multi-primary mode)
MySQL Group Replication搭建
06-03
以下是MySQL Group Replication的搭建步骤： 1. 安装MySQL Group Replication插件 在MySQL安装完成后，需要在MySQL的配置文件中启用Group Replication插件。在配置文件中添加以下内容： ``` [mysqld] plugin-load=...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值