InnoDB ReplicaSet

最新推荐文章于 2023-03-17 14:39:47 发布
最新推荐文章于 2023-03-17 14:39:47 发布
阅读量606 收藏
点赞数
分类专栏： 数据库 文章标签： mysql replicaset innodb
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/L835311324/article/details/107836603
版权

文章目录

简介

MySQL Shell的AdminAPI新增了 对InnoDB ReplicaSet的支持，可以用与InnoDB Cluster类似的方式管理一组运行基于GTID的异步复制的MySQL实例。InnoDB ReplicaSet由一个主和多个从组成。您可以使用ReplicaSet对象和AdminAPI操作，例如检查InnoDB ReplicaSet的状态，并在发生故障时手动故障转移到新的主数据库。与InnoDB Cluster类似，MySQL Router支持针对InnoDB ReplicaSet的引导，这意味着可以自动配置MySQL Router以使用InnoDB ReplicaSet，而无需手动配置它。这使InnoDB ReplicaSet成为启动和运行MySQL复制和MySQL Router的快速简便方法，使其非常适合横向扩展读取。

与InnoDB Cluster相比，InnoDB ReplicaSet具有如下限制：

  • 没有自动故障切换，如果主不可用，则需要手动触发故障转移
  • 无法防止因意外或不可用导致的部分数据丢失(因为是异步复制)
  • 无法防止崩溃或不可用后出现不一致情况。

部署InnoDB ReplicaSet

要求

  • 仅支持运行MySQL 8.0及更高版本的实例
  • 仅支持基于GTID的复制，二进制日志文件位置复制与InnoDB ReplicaSet不兼容
  • 仅支持基于行的复制（RBR），不支持基于语句的复制（SBR）
  • 不支持复制过滤器
  • 在任何实例下都不允许Unmanaged replication channels
  • 一个ReplicaSet最多包含一个主实例，并且支持一个或多个第二实例。尽管可以添加到副本集的辅助副本数量没有限制，但是连接到副本集的每个MySQL Router都会监视每个实例。因此，添加到ReplicaSet的实例越多，必须执行的监视越多。
  • ReplicaSet必须完全由MySQL Shell管理。例如，复制帐户由MySQL Shell创建和管理。不支持在MySQL Shell之外对实例进行配置更改，例如，直接使用SQL语句更改主实例。应该始终将MySQL Shell与InnoDB ReplicaSet一起使用。

环境

规划

IP:PORT主机名server-id系统版本MySQL版本MySQL Shell版本MySQL Router版本
192.168.240.81:3310innodb_cluster_0181CentOS7.68.0.21mysql-shell-8.0.21mysql-router-8.0.21
192.168.240.82:3310innodb_cluster_0282CentOS7.68.0.21--
192.168.240.83:3310innodb_cluster_0383CentOS7.68.0.21--

MySQL Shell ,Rpm包下载地址:https://dev.mysql.com/downloads/shell/

MySQL Router,Rpm包下载地址:https://dev.mysql.com/downloads/router/

MySQL ，二进制包下载地址：https://dev.mysql.com/downloads/mysql/

前期准备

  1. 设置主机名

InnoDB ReplicaSet集群内部节点主机名必须唯一，可以通过hostname命令设置

按照先前规划，填写/etc/hosts文件

[root@localhost ~]# cat /etc/hosts
192.168.240.81 innodb_rs_01
192.168.240.82 innodb_rs_02
192.168.240.83 innodb_rs_03

修改本机主机名(每台机根据情况修改自己主机名)

hostnamectl  set-hostname innodb_rs_01
  1. 关闭防火墙与selinux
systemctl  stop firewalld
setenforce  0

安装MySQL

把MySQL二进制安装包上传到/usr/local/src目录下

cd /usr/local/src
tar xf mysql-8.0.21-linux-glibc2.17-x86_64-minimal.tar.xz
mv mysql-8.0.21-linux-glibc2.17-x86_64-minimal /usr/local/mysql8.0
echo 'export  PATH=/usr/local/mysql8.0/bin:$PATH' >> /etc/profile
. /etc/profile

创建目录结构(所有节点)

useradd -M -s /sbin/nologin  mysql
mkdir -pv  /datadir/{temp,log,data}
chown -R mysql:mysql /datadir

初始化数据库(所有节点)

mysqld  --datadir=/datadir/data --user=mysql --initialize-insecure
chown -R mysql:mysql /datadir

修改配置文件(所有节点)

[mysqld]
basedir=/usr/local/mysql8.0
user=mysql
port=3310
datadir=/datadir/data
log-error=/datadir/log/err.log
pid-file=/datadir/temp/mysqld.pid
socket=/datadir/temp/mysqld.sock
symbolic-links=0
server_id=81
gtid-mode=on
enforce-gtid-consistency=true

log_bin=/datadir/log/binlog
binlog_format=ROW

[client]
socket=/datadir/temp/mysqld.sock

只需要修改server_id这一项即可(保证所有MySQL服务器都不同)

启动数据库(所有节点)

mysqld_safe --defaults-file=/etc/my.cnf --daemonize

进入mysql，创建ir用户(所有节点)

set sql_log_bin=OFF;
CREATE USER 'ir'@'%' IDENTIFIED BY '123456';
GRANT ALL ON *.* to 'ir'@'%' WITH GRANT OPTION;
set sql_log_bin=ON;

安装MySQL Shell

上传MySQL Shell包到innodb_rs_01的/usr/local/src目录下

cd /usr/local/src
yum install mysql-shell-8.0.21-1.el7.x86_64.rpm -y

配置InnoDB ReplicaSet

  1. 进入MySQL Shell（innodb_rs_01节点执行）
mysqlsh
  1. 创建rsadmin的集群管理员(此处以innodb_rs_01节点为例)
 MySQL  JS >  dba.configureReplicaSetInstance('ir@innodb_rs_01:3310', {clusterAdmin: "'rsadmin'@'%'"});
Please provide the password for 'ir@innodb_rs_01:3310': ******* # 此处填写ir用户的密码
Save password for 'ir@innodb_rs_01:3310'? [Y]es/[N]o/Ne[v]er (default No): y # 是否记住密码，如果选择y则下次连接无需重新输入密码
Configuring local MySQL instance listening at port 3310 for use in an InnoDB ReplicaSet...

This instance reports its own address as innodb_rs_01:3310
Clients and other cluster members will communicate with it through this address by default. If this is not correct, the report_host MySQL system variable should be changed.
Password for new account: ******# 此处填写'rsadmin'@'%' 想要设置的密码
Confirm password: ****** # 确认'rsadmin'@'%'密码

The instance 'innodb_rs_01:3310' is valid to be used in an InnoDB ReplicaSet.
Cluster admin user 'rsadmin'@'%' created.
The instance 'innodb_rs_01:3310' is already ready to be used in an InnoDB ReplicaSet. # 表示已经就绪，可以创建innodb ReplicaSet
  1. dba.configureReplicaSetInstance()函数可以创建管理员帐户。使用正确的权限来创建帐户来管理InnoDB集群和InnoDB副本集。
  2. 在同一集群或副本集的所有实例中，管理员帐户必须具有相同的用户名和密码。
  1. 创建Innodb ReplicaSet（innodb_rs_01节点执行）
mysql-js> \connect ir@innodb_rs_01:3310
MySQL  innodb_rs_01:3310 ssl  JS > var rs = dba.createReplicaSet("example") 
A new replicaset with instance 'innodb_rs_01:3310' will be created.

* Checking MySQL instance at innodb_rs_01:3310

This instance reports its own address as innodb_rs_01:3310
innodb_rs_01:3310: Instance configuration is suitable.

* Updating metadata...

ReplicaSet object successfully created for innodb_rs_01:3310.
Use rs.addInstance() to add more asynchronously replicated instances to this replicaset and rs.status() to check its status.
  1. 查看ReplicaSet状态（innodb_rs_01节点执行）
 MySQL  innodb_rs_01:3310 ssl  JS > rs.status()
{
    "replicaSet": { 
        "name": "example", # 复制集名称
        "primary": "innodb_rs_01:3310", # 主节点
        "status": "AVAILABLE", # 状态：可用
        "statusText": "All instances available.", # 状态备注信息
        "topology": { # 当前拓扑
            "innodb_rs_01:3310": { 
                "address": "innodb_rs_01:3310", # 复制集通讯地址
                "instanceRole": "PRIMARY", # 角色，主/从
                "mode": "R/W", # 模式，主节点可读可写，从节点只读
                "status": "ONLINE" # 节点状态
            }
        },
        "type": "ASYNC" # 复制类型 异步
    }
}
  1. 添加innodb_rs_02:3310实例进入集群（innodb_rs_01节点执行）
 MySQL  innodb_rs_01:3310 ssl  JS > rs.addInstance('innodb_rs_02:3310')
Adding instance to the replicaset...

* Performing validation checks

This instance reports its own address as innodb_rs_02:3310
innodb_rs_02:3310: Instance configuration is suitable.

* Checking async replication topology...

* Checking transaction state of the instance...

NOTE: The target instance 'innodb_rs_02:3310' has not been pre-provisioned (GTID set is empty). The Shell is unable to decide whether replication can completely recover its state.
The safest and most convenient way to provision a new instance is through automatic clone provisioning, which will completely overwrite the state of 'innodb_rs_02:3310' with a physical snapshot from an existing replicaset member. To use this method by default, set the 'recoveryMethod' option to 'clone'.

WARNING: It should be safe to rely on replication to incrementally recover the state of the new instance if you are sure all updates ever executed in the replicaset were done with GTIDs enabled, there are no purged transactions and the new instance contains the same GTID set as the replicaset or a subset of it. To use this method by default, set the 'recoveryMethod' option to 'incremental'.

# 输入I，选择增量恢复，需要确保所有实例GTID打开，以及没有被purged的事务，且gitd set必须是主节点的子集
Please select a recovery method [C]lone/[I]ncremental recovery/[A]bort (default Clone): i  
* Updating topology
** Configuring innodb_rs_02:3310 to replicate from innodb_rs_01:3310
** Waiting for new instance to synchronize with PRIMARY...

The instance 'innodb_rs_02:3310' was added to the replicaset and is replicating from innodb_rs_01:3310.
  1. 添加innodb_rs_03:3310实例进入集群（innodb_rs_01节点执行）
 MySQL  innodb_rs_01:3310 ssl  JS > rs.addInstance('innodb_rs_03:3310')
Adding instance to the replicaset...

* Performing validation checks

This instance reports its own address as innodb_rs_03:3310
innodb_rs_03:3310: Instance configuration is suitable.

* Checking async replication topology...

* Checking transaction state of the instance...

NOTE: The target instance 'innodb_rs_03:3310' has not been pre-provisioned (GTID set is empty). The Shell is unable to decide whether replication can completely recover its state.
The safest and most convenient way to provision a new instance is through automatic clone provisioning, which will completely overwrite the state of 'innodb_rs_03:3310' with a physical snapshot from an existing replicaset member. To use this method by default, set the 'recoveryMethod' option to 'clone'.

WARNING: It should be safe to rely on replication to incrementally recover the state of the new instance if you are sure all updates ever executed in the replicaset were done with GTIDs enabled, there are no purged transactions and the new instance contains the same GTID set as the replicaset or a subset of it. To use this method by default, set the 'recoveryMethod' option to 'incremental'.

# 输入I，选择增量恢复，需要确保所有实例GTID打开，以及没有被purged的事务，且gitd set必须是主节点的子集
Please select a recovery method [C]lone/[I]ncremental recovery/[A]bort (default Clone): i
* Updating topology
** Configuring innodb_rs_03:3310 to replicate from innodb_rs_01:3310
** Waiting for new instance to synchronize with PRIMARY...

The instance 'innodb_rs_03:3310' was added to the replicaset and is replicating from innodb_rs_01:3310.
  1. 查看集群状态
MySQL  innodb_rs_01:3310 ssl  JS > rs.status()
{
    "replicaSet": {
        "name": "example",# 复制集名称
        "primary": "innodb_rs_01:3310",# 主节点
        "status": "AVAILABLE",# 状态：可用
        "statusText": "All instances available.", # 状态备注信息
        "topology": { # 当前拓扑
            "innodb_rs_01:3310": {
                "address": "innodb_rs_01:3310", # 复制集通讯地址
                "instanceRole": "PRIMARY", # 角色，主/从
                "mode": "R/W", # 模式，主节点可读可写，从节点只读
                "status": "ONLINE" # 节点状态
            },
            "innodb_rs_02:3310": {
                "address": "innodb_rs_02:3310",
                "instanceRole": "SECONDARY",
                "mode": "R/O",
                "replication": {
                    "applierStatus": "APPLIED_ALL",
                    "applierThreadState": "Slave has read all relay log; waiting for more updates",
                    "receiverStatus": "ON",
                    "receiverThreadState": "Waiting for master to send event",
                    "replicationLag": null
                },
                "status": "ONLINE"
            },
            "innodb_rs_03:3310": {
                "address": "innodb_rs_03:3310",
                "instanceRole": "SECONDARY",
                "mode": "R/O",
                "replication": {
                    "applierStatus": "APPLIED_ALL",
                    "applierThreadState": "Slave has read all relay log; waiting for more updates",
                    "receiverStatus": "ON",
                    "receiverThreadState": "Waiting for master to send event",
                    "replicationLag": null
                },
                "status": "ONLINE"
            }
        },
        "type": "ASYNC" # 复制类型 异步
    }
}

配置MySQL Router

上传MySQL Router RPM包innodb_rs_03节点上的/usr/local/src目录下

cd /usr/local/src
yum install mysql-router-community-8.0.21-1.el7.x86_64.rpm  -y

MySQL Router对接InnoDB Cluster

mysqlrouter --bootstrap ir@innodb_rs_01:3310 --user=mysqlrouter

启动MySQL Router

systemctl start mysqlrouter

会启动4个端口

  • 6446 - 对于传统MySQL协议读写会话，MySQL路由器将传入连接重定向到Primary服务器实例。
  • 6447 - 对于传统MySQL协议只读会话，MySQL路由器将传入连接重定向到其中一个从服务器实例。
  • 64460 - 对于X协议读写会话，MySQL路由器将传入连接重定向到Primary服务器实例。
  • 64470 - 对于X协议只读会话，MySQL路由器将传入连接重定向到其中一个从服务器实例。

连接读写端口,进行测试

# mysql -uir -p -P6446 -h192.168.240.83
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 109
Server version: 8.0.21 MySQL Community Server - GPL

Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved.

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> select @@server_id;
+-------------+
| @@server_id |
+-------------+
|          81 |
+-------------+
1 row in set (0.00 sec)

InnoDB ReplicaSet日常管理

  1. 连接InnoDB 复制集

    # 连接其中一个复制集节点
 MySQL  JS > \c ir@innodb_rs_02:3310
# 获取复制集连接
 MySQL  innodb_rs_02:3310 ssl  JS > var rs = dba.getReplicaSet()
# 后续就可以直接使用rs对象管理集群

  2. 查看集群状态

     MySQL  innodb_rs_02:3310 ssl  JS > rs.status()
{
    "replicaSet": {
        "name": "example",
        "primary": "innodb_rs_01:3310",
        "status": "AVAILABLE",
        "statusText": "All instances available.",
        "topology": {
            "innodb_rs_01:3310": {
                "address": "innodb_rs_01:3310",
                "instanceRole": "PRIMARY",
                "mode": "R/W",
                "status": "ONLINE"
            },
            "innodb_rs_02:3310": {
                "address": "innodb_rs_02:3310",
                "instanceRole": "SECONDARY",
                "mode": "R/O",
                "replication": {
                    "applierStatus": "APPLIED_ALL",
                    "applierThreadState": "Slave has read all relay log; waiting for more updates",
                    "receiverStatus": "ON",
                    "receiverThreadState": "Waiting for master to send event",
                    "replicationLag": null
                },
                "status": "ONLINE"
            },
            "innodb_rs_03:3310": {
                "address": "innodb_rs_03:3310",
                "instanceRole": "SECONDARY",
                "mode": "R/O",
                "replication": {
                    "applierStatus": "APPLIED_ALL",
                    "applierThreadState": "Slave has read all relay log; waiting for more updates",
                    "receiverStatus": "ON",
                    "receiverThreadState": "Waiting for master to send event",
                    "replicationLag": null
                },
                "status": "ONLINE"
            }
        },
        "type": "ASYNC"
    }
}

  3. 新增实例

    # 新增innodb_rs_03:3310节点
MySQL  innodb_rs_02:3310 ssl  JS > rs.addInstance('innodb_rs_03:3310')

  4. 强制切换主节点

    # 当主节点down了，就需要强制切换主
rs.forcePrimaryInstance('innodb_rs_03:3310')

  5. 设置主节点

     MySQL  innodb_rs_02:3310 ssl  JS > rs.setPrimaryInstance('innodb_rs_03:3310')
innodb_rs_03:3310 will be promoted to PRIMARY of 'example'.
The current PRIMARY is innodb_rs_01:3310.

* Connecting to replicaset instancess
** Connecting to innodb_rs_01:3310
** Connecting to innodb_rs_02:3310
** Connecting to innodb_rs_03:3310
** Connecting to innodb_rs_01:3310
** Connecting to innodb_rs_02:3310
** Connecting to innodb_rs_03:3310

* Performing validation checks
** Checking async replication topology...
** Checking transaction state of the instance...

* Synchronizing transaction backlog at innodb_rs_03:3310

* Updating metadata

* Acquiring locks in replicaset instances
** Pre-synchronizing SECONDARIES
** Acquiring global lock at PRIMARY
** Acquiring global lock at SECONDARIES

* Updating replication topology
** Configuring innodb_rs_01:3310 to replicate from innodb_rs_03:3310
** Changing replication source of innodb_rs_02:3310 to innodb_rs_03:3310

innodb_rs_03:3310 was promoted to PRIMARY.

  6. 移除实例

    # 从ReplicaSet中移除innodb_rs_03:3310节点
MySQL  innodb_rs_02:3310 ssl  JS > rs.removeInstance('innodb_rs_03:3310')

  7. 查看MySQL Router信息

     MySQL  innodb_rs_02:3310 ssl  JS > rs.listRouters()
{
    "replicaSetName": "example",
    "routers": {
        "innodb_rs_03::system": {
            "hostname": "innodb_rs_03",
            "lastCheckIn": "2020-08-06 00:09:40",
            "roPort": 6447,
            "roXPort": 64470,
            "rwPort": 6446,
            "rwXPort": 64460,
            "version": "8.0.21"
        }
    }
}

    参考文档

)


7. 查看MySQL Router信息

```js
 MySQL  innodb_rs_02:3310 ssl  JS > rs.listRouters()
{
    "replicaSetName": "example",
    "routers": {
        "innodb_rs_03::system": {
            "hostname": "innodb_rs_03",
            "lastCheckIn": "2020-08-06 00:09:40",
            "roPort": 6447,
            "roXPort": 64470,
            "rwPort": 6446,
            "rwXPort": 64460,
            "version": "8.0.21"
        }
    }
}

参考文档

  • https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-replicasets.html
十五十六
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
MySQL innodb 技术内幕
09-16
MySQL InnoDB 技术内幕 MySQL InnoDB 存储引擎是 MySQL 关系数据库管理系统中最常用的存储引擎之一。InnoDB 存储引擎是 MySQL 的默认存储引擎，它提供了高性能、高可靠性的存储功能。 数据库和实例的区别 -------...
InnoDB源码解析
01-29
MySQL的Innodb引擎架构设计与分析，非常详细，且从架构高度理解，非常好。
MySQL8.0.19的InnoDB ReplicaSet
Evelyn_Lv的博客
02-13 393
以下文章来源于MySQL解决方案工程师 ，作者徐轶韬 MySQL8.0.19里面推出了一个新功能，InnoDB ReplicaSet，我暂且管它叫做叫做复制集。那么这个复制集是做什么用的呢？为何要推出这样一款产品呢？它将如何使用呢？这篇文章里我将会简单的介绍一下它。 InnoDB ReplicaSet由一个主节点和多个从节点组成，与传统主从复制的主从节点非常类似，所有的节点必须基于GTID，并...
第 22 章 InnoDB ReplicaSet
影三人
11-09 158
《MySQL 8.0 参考手册翻译》第12章 InnoDB ReplicaSet
MySQL Innodb ReplicaSet
分享既学习
03-17 851
MySQL Innodb ReplicaSet 是 MySQL 团队在 2020 年推出的一款产品，用来帮助用户快速部署和管理主从复制，在数据库层仍然使用的是主从复制技术。
详解 InnoDB ReplicaSet
影三人
12-16 928
的关键字是AdminAPI，MySQL Shell，MySQL Router，MySQL 异步复制。其功能同比传统 MyCat 等中间构成的 MMM 、MHA 主从架构相差不大，可以理解为 MySQL 官方实现发行版本，但 MySQL Shell 这个 MySQL 未来主打的 DevOps 工具还是更具优势的。
新特性解读 | InnoDB ReplicaSet：MySQL 副本集初体验
ActionTech的博客
03-02 381
作者：任仲禹 一、InnoDB ReplicaSet 介绍 MySQL 副本集（官方名称：MySQL InnoDB ReplicaSet）在 MySQL 8.0.19 版本（2020-01-13 Released）之后开始支持，本质还是是基于 GTID 的异步复制 角色分为 Primary 和 Secondary Primary 即传统意义上的 Master，一个副本集只允许一个 Seco...
Innodb核心内幕
06-22
innodb核心内幕，完整的探索整个innodb的秘密。对于mysql dba进阶非常有用。
mysql，innodb索引介绍
最新发布
05-06
MySQL数据库的InnoDB存储引擎广泛使用BTree索引来优化查询性能。BTree索引是一种常见的索引类型，尤其适用于范围查询和排序操作。在MySQL中，InnoDB存储引擎的索引分为聚簇索引（主键索引）和非聚簇索引（二级索引）...
MySQL不支持InnoDB的解决方法
09-11
MySQL是世界上最受欢迎的关系型数据库管理系统之一，它支持多种存储引擎，其中包括InnoDB和MyISAM。InnoDB引擎因其强大的事务处理能力、行级锁定以及外键支持而被广泛使用，尤其是在需要高度数据完整性和一致性的...
MySQL高可用架构之InnoDB ReplicaSet部署
Sebastien23的博客
03-04 1102
可以通过MySQL Shell快速搭建及管理主从复制，避免了搭建主从复制时大量的手动操作。InnoDB ReplicaSet至少由两台MySQL服务器实例组成，提供MySQL主从复制功能。MySQL Router可以为ReplicaSet提供应用程序的透明路由和读写分离，建议与应用安装在同一台服务器上。可以看到，MySQL Router生成了四个连接路由，两个读写和两个只读。重新通过MySQL Router建立连接后，可以看到主实例已经更新为。发生主从切换后，已有的连接会断开，需要重新建立连接。
MySQL8.0使用mysqlsh配置主从复制 InnoDB ReplicaSet
IOsetting的专栏
10-17 465
InnoDB ReplicaSet InnoDB ReplicaSet 由一个主节点和多个从节点构成. 可以使用ReplicaSet对象和AdminAPI操作管理复制集, 例如检查InnoDB复制集的状态, 并在发生故障时手动故障转移到新的主服务器. 与InnoDB cluster类似, MySQL Router 支持针对InnoDB ReplicaSet 的引导, 这意味着可以自动配置MySQ...
第22章 InnoDB ReplicaSet
一线大码
04-04 170
官方文档地址：Chapter 22 InnoDB ReplicaSet 本章介绍 MySQL InnoDB ReplicaSet，它结合了 MySQL 技术，使您能够部署和管理 第17章 复制。这是 InnoDB ReplicaSet 的一个高级概述，有关完整文档，请参见 MySQL InnoDB ReplicaSet。 InnoDB ReplicaSet 至少由两个 MySQL 服务器实例组成，并且提供您熟悉的所有 MySQL 复制功能，例如读取横向扩展和数据安全性。InnoDB ReplicaSet
mysql redis hbase_MySQL高可用新方案|MySQL InnoDB ReplicaSet介绍
weixin_39564807的博客
11-28 66
在2020年1月13日，MySQL官方发布了MySQL8.0.19。在新的版本中，MySQL官方引入了新的高可用解决方案MySQL InnoDB ReplicaSet。一、介绍(图来自官方博客mysqlserverteam.com)MySQL InnoDB ReplicaSet是基于MySQL 主从复制的一种高可用方案，能够实现手动切换/故障转移。InnoDB ReplicaSet使用到...
【MySQL Shell】第 9 章 MySQL InnoDB ReplicaSet
影三人
01-18 1070
【MySQL Shell】第 9 章 MySQL InnoDB ReplicaSet
MySQL Shell：02 部署InnoDB ReplicaSet
老叶茶馆
02-13 1248
点击蓝字关注我们2020年1月除了来源信息如迷之故事会一般的冠状病毒外，MySQL 官方发布了全新的8.0.19版本，而其中最大的亮点莫过于ReplicaSet功能。InnoDB Rep...
【MySQL Shell】9.2 配置 InnoDB ReplicaSet 实例
影三人
01-18 152
【MySQL Shell】9.2 配置 InnoDB ReplicaSet 实例

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值