MySQL InnoDB Cluster搭建安装
环境介绍：
这里的MySQL Innodb Cluster搭建环境如下所示,总共有三台机器搭建MySQL InnoDB Cluster：
操作系统： Red Hat Enterprise Linux release 8.8 (Ootpa)
数据库版本：8.0.35 MySQL Community Server - GPL
第一步：环境检查与配置
1：防火墙配置
测试环境可以关闭防火墙，生产环境一般会开启防火墙。在防火墙上设置相关IP和端口。根据实际情况进行设置（需要root权限，一般由系统管理员设置）
关于如何设置防火墙限定IP地址，这里不做过多介绍，其实配置也很简单。端口号根据实际情况配置。
# systemctl status firewalld.service
# systemctl stop firewalld.service
# systemctl status firewalld.service
# systemctl disable firewalld.service
2：关闭或配置SELinux
检查是否关闭selinux
# /usr/sbin/sestatus
SELinux status: disabled
修改SELinux配置文件
如果没有关闭selinux的话，我们建议关闭selinux，可以通过修改selinux的配置文件，将SELINUX=enforcing改为SELINUX=disabled。
#vi /etc/selinux/config
SELINUX=disabled
如果不想重启，如果想验证一下，可以重启一下服务器。
setenforce 0
getenforce
如果公司要求开启SELinux的话， 必须设置SELinux 策略，在SELinux 下允许MySQL连接
sudo setsebool -P mysql_connect_any 1
3：配置IP与主机名映射
编辑/etc/hosts
#MySQL InnoDB Cluster
192.168.9.200 mysqlu01
192.168.9.201 mysqlu02
192.168.9.202 mysqlu03
[注意]：三台MySQL服务器都必须设置，不能只设置一台服务器。请注意，不要遗漏。
4：修改内核参数
/etc/security/limits.conf
mysql hard nofile 65536
mysql soft nofile 65536
或者
* hard nofile 65536
* soft nofile 65536
5：配置标准大页
grep -i huge /proc/meminfo
建议开启标准大页，这样更有利于性能。
6：禁用透明大页
第二步：安装MySQL实例
1：安装MySQL实例
使用mysql_auto_install.sh脚本自动安装MySQL单实例，如果常规的安装MySQL实例，参考文档“MySQL 8.0的二进制安装文档.docx” ，三台（多台）服务器上安装MySQL实例
$ cd /data/soft
$ sh mysql_auto_install.sh
2：修改参数文件中MGR参数配置
修改server_id=xxxx #规则，取IP地址的最后一位,然后在my.cnf中添加下面配置
##########################################################################################################################
# GTID SETTING
##########################################################################################################################
plugin_dir=/opt/mysql/mysql8.0/lib/plugin #设置plugin的路径
enforce_gtid_consistency = ON #强制GTID的一致性
gtid-mode=ON #开启GTID,必须开启
master-info-repository=TABLE
relay-log-info-repository=TABLE #记录同步的信息,便于管理和恢复
log-slave-updates = ON #需要记录事务的binlog,用作以后的恢复用,哪怕不是写入点,也需要
binlog-checksum=NONE #MGR本身不支持binlog的checksum校验
slave-parallel-workers=8 #GTID的SQL线程
slave_preserve_commit_order=ON #GTID配置，SQL线程按照顺序重放事物
#slave-parallel-type=LOGICAL_CLOCK #SQL线程工作模式。有两种。
disabled_storage_engines="MyISAM,BLACKHOLE,FEDERATED,ARCHIVE,MEMORY"
##########################################################################################################################
##########################################################################################################################
# 组复制设置
##########################################################################################################################
#记录事务的算法,官网建议设置该参数使用 XXHASH64 算法
transaction_write_set_extraction = XXHASH64
plugin_load_add='group_replication.so'
#是否随服务器启动而自动启动组复制,不建议直接启动,怕故障恢复时有扰乱数据准确性的特殊情况
#loose-group_replication_start_on_boot = OFF
group_replication_start_on_boot = OFF
#开启引导模式,添加组成员，用于第一次搭建MGR或重建MGR的时候使用,只需要在集群内的其中一台开启,
#loose-group_replication_bootstrap_group = OFF
group_replication_bootstrap_group = OFF
#IP地址白名单,默认只添加127.0.0.1,不会允许来自外部主机的连接,按需安全设置
#loose-group_replication_ip_whitelist = '127.0.0.1/8,192.168.9.0/24'
group_replication_ip_allowlist = '127.0.0.1/8,192.168.9.0/24'
#是否启动单主模式，如果启动，则本实例是主库，提供读写，其他实例仅提供读,如果为off就是多主模式了
loose-group_replication_single_primary_mode = ON
##ssl for mgr
group_replication_ssl_mode = REQUIRED
group_replication_recovery_use_ssl = ON
binlog_transaction_dependency_tracking=WRITESET
##########################################################################################################################
注意，这里使用mysql shell创建InnoDB Cluster时，不需要在参数文件中设置group_replication_group_name等参数，有些版本的参数也有所出入，请以实际情况为准。
修改后重启每一台MySQL服务。
$ sudo systemctl stop mysqld.service
$ sudo systemctl start mysqld.service
$ sudo systemctl status mysqld.service
安装MySQL Shell
# yum localinstall mysql-shell-8.0.35-1.el8.x86_64.rpm
这里使用root用户安装。因为mysql用户没有权限安装。可以只安装一台MySQL服务器，也可以三台都安装。
创建数据库用户
##手动创建需要设置log bin 为0，创建完成后设置回1，所有服务器执行
SET SQL_LOG_BIN=0;
CREATE USER icadmin@'192.168.9.%' IDENTIFIED BY '******';
GRANT ALL ON *.* TO icadmin@'192.168.9.%' WITH GRANT OPTION;
SET SQL_LOG_BIN=1;
注意：所有MySQL节点需要执行创建用户操作，此用户临时使用，配置完集群后删除。
mysqlsh
\c [email protected]:7306
或
mysqlsh -h 192.168.9.200 -P 7306 -u icadmin -p
检查实例是否符合InnoDB Cluster的参数及权限配置要求
dba.checkInstanceConfiguration('[email protected]:7306')
dba.checkInstanceConfiguration('[email protected]:7306')
dba.checkInstanceConfiguration('[email protected]:7306')
检查符合InnoDB Cluster的参数、权限配置符合要求的话，则会返回status为OK，否则会提示不符合要求信息。
MySQL 192.168.9.200:7306 ssl JS > dba.checkInstanceConfiguration('[email protected]:7306')
Please provide the password for '[email protected]:7306': ****************
Save password for '[email protected]:7306'? [Y]es/[N]o/Ne[v]er (default No): yes
Validating MySQL instance at mysqlu02:7306 for use in an InnoDB cluster...
This instance reports its own address as mysqlu02:7306
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.
Checking whether existing tables comply with Group Replication requirements...
No incompatible tables detected
Checking instance configuration...
Instance configuration is compatible with InnoDB cluster
The instance 'mysqlu02:7306' is valid to be used in an InnoDB cluster.
{
"status": "ok"
}
MySQL 192.168.9.200:7306 ssl JS >
如果MySQL的参数不符合要求，则上面输出信息"status"不为"ok",则必须修改相关参数参数，重新检测。
初始化InnoDB Cluster相关配置
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
或者
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"},clusterAdminPassword:"*****"});
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"},clusterAdminPassword:"*****"});
dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"},clusterAdminPassword:"*****"});
具体执行过程如下所示：
MySQL 192.168.9.200:7306 ssl JS > dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
Configuring local MySQL instance listening at port 7306 for use in an InnoDB cluster...
This instance reports its own address as mysqlu01:7306
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.
User 'icadmin'@'192.168.9.%' already exists and will not be created.
applierWorkerThreads will be set to the default value of 4.
The instance 'mysqlu01:7306' is valid to be used in an InnoDB cluster.
The instance 'mysqlu01:7306' is already ready to be used in an InnoDB cluster.
Successfully enabled parallel appliers.
MySQL 192.168.9.200:7306 ssl JS > dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
Configuring MySQL instance at mysqlu02:7306 for use in an InnoDB cluster...
This instance reports its own address as mysqlu02:7306
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.
User 'icadmin'@'192.168.9.%' already exists and will not be created.
applierWorkerThreads will be set to the default value of 4.
The instance 'mysqlu02:7306' is valid to be used in an InnoDB cluster.
The instance 'mysqlu02:7306' is already ready to be used in an InnoDB cluster.
Successfully enabled parallel appliers.
MySQL 192.168.9.200:7306 ssl JS > dba.configureInstance('[email protected]:7306', {clusterAdmin: "'icadmin'@'192.168.9.%'"});
Configuring MySQL instance at mysqlu03:7306 for use in an InnoDB cluster...
This instance reports its own address as mysqlu03:7306
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.
User 'icadmin'@'192.168.9.%' already exists and will not be created.
applierWorkerThreads will be set to the default value of 4.
The instance 'mysqlu03:7306' is valid to be used in an InnoDB cluster.
The instance 'mysqlu03:7306' is already ready to be used in an InnoDB cluster.
Successfully enabled parallel appliers.
MySQL 192.168.9.200:7306 ssl JS >
创建集群
var cluster = dba.createCluster('gsp_cluster');
具体操作如下所示：
MySQL 192.168.9.200:7306 ssl JS > var cluster = dba.createCluster('gsp_cluster');
A new InnoDB Cluster will be created on instance 'mysqlu01:7306'.
Validating instance configuration at 192.168.9.200:7306...
This instance reports its own address as mysqlu01:7306
Instance configuration is suitable.
NOTE: Group Replication will communicate with other members using 'mysqlu01:7306'. Use the localAddress option to override.
* Checking connectivity and SSL configuration...
Creating InnoDB Cluster 'gsp_cluster' on 'mysqlu01:7306'...
Adding Seed Instance...
Cluster successfully created. Use Cluster.addInstance() to add MySQL instances.
At least 3 instances are needed for the cluster to be able to withstand up to
one server failure.
MySQL 192.168.9.200:7306 ssl JS >
查看创建集群状态
var cluster = dba.getCluster()
cluster.status()
具体输出如下所示：
MySQL 192.168.9.200:7306 ssl JS > var cluster = dba.getCluster()
MySQL 192.168.9.200:7306 ssl JS > cluster.status()
{
"clusterName": "gsp_cluster",
"defaultReplicaSet": {
"name": "default",
"primary": "mysqlu01:7306",
"ssl": "REQUIRED",
"status": "OK_NO_TOLERANCE",
"statusText": "Cluster is NOT tolerant to any failures.",
"topology": {
"mysqlu01:7306": {
"address": "mysqlu01:7306",
"memberRole": "PRIMARY",
"mode": "R/W",
"readReplicas": {},
"replicationLag": "applier_queue_applied",
"role": "HA",
"status": "ONLINE",
"version": "8.0.33"
}
},
"topologyMode": "Single-Primary"
},
"groupInformationSourceMember": "mysqlu01:7306"
}
MySQL 192.168.9.200:7306 ssl JS >
添加节点到集群
var cluster=dba.getCluster()
cluster.addInstance('[email protected]:7306')
cluster.status()
cluster.addInstance('[email protected]:7306')
cluster.status()
部分输出如下所示：
MySQL 192.168.9.200:7306 ssl JS > cluster.addInstance('[email protected]:7306')
NOTE: The target instance 'mysqlu03:7306' has not been pre-provisioned (GTID set is empty). The Shell is unable to decide whether incremental state recovery can correctly provision it.
The safest and most convenient way to provision a new instance is through automatic clone provisioning, which will completely overwrite the state of 'mysqlu03:7306' with a physical snapshot from an existing cluster member. To use this method by default, set the 'recoveryMethod' option to 'clone'.
The incremental state recovery may be safely used if you are sure all updates ever executed in the cluster were done with GTIDs enabled, there are no purged transactions and the new instance contains the same GTID set as the cluster or a subset of it. To use this method by default, set the 'recoveryMethod' option to 'incremental'.
Please select a recovery method [C]lone/[I]ncremental recovery/[A]bort (default Clone): C
Validating instance configuration at 192.168.9.202:7306...
This instance reports its own address as mysqlu03:7306
Instance configuration is suitable.
NOTE: Group Replication will communicate with other members using 'mysqlu03:7306'. Use the localAddress option to override.
* Checking connectivity and SSL configuration...
A new instance will be added to the InnoDB Cluster. Depending on the amount of
data on the cluster this might take from a few seconds to several hours.
Adding instance to the cluster...
Monitoring recovery process of the new cluster member. Press ^C to stop monitoring and let it continue in background.
Clone based state recovery is now in progress.
NOTE: A server restart is expected to happen as part of the clone process. If the
server does not support the RESTART command or does not come back after a
while, you may need to manually start it back.
* Waiting for clone to finish...
NOTE: mysqlu03:7306 is being cloned from mysqlu02:7306
** Stage DROP DATA: Completed
** Clone Transfer FILE COPY ============================================================ 0% Not Started PAGE COPY ============================================================ 0% Not Started REDO COPY ============================================================ 0% Not Started** Clone Transfer FILE COPY ============================================================ 0% In Progress PAGE COPY ============================================================ 0% Not Started REDO COPY ============================================================ 0% Not Started** Clone Transfer FILE COPY ############################################################ 100% Completed PAGE COPY ############################################################ 100% Completed REDO COPY ############################################################ 100% Completed
NOTE: mysqlu03:7306 is shutting down...
* Waiting for server restart... ready
* mysqlu03:7306 has restarted, waiting for clone to finish...
** Stage RESTART: Completed
* Clone process has finished: 73.65 MB transferred in about 1 second (~73.65 MB/s)
State recovery already finished for 'mysqlu03:7306'
The instance 'mysqlu03:7306' was successfully added to the cluster.
MySQL 192.168.9.200:7306 ssl JS > cluster.status()
{
"clusterName": "gsp_cluster",
"defaultReplicaSet": {
"name": "default",
"primary": "mysqlu01:7306",
"ssl": "REQUIRED",
"status": "OK",
"statusText": "Cluster is ONLINE and can tolerate up to ONE failure.",
"topology": {
"mysqlu01:7306": {
"address": "mysqlu01:7306",
"memberRole": "PRIMARY",
"mode": "R/W",
"readReplicas": {},
"replicationLag": "applier_queue_applied",
"role": "HA",
"status": "ONLINE",
"version": "8.0.33"
},
"mysqlu02:7306": {
"address": "mysqlu02:7306",
"memberRole": "SECONDARY",
"mode": "R/O",
"readReplicas": {},
"replicationLag": "applier_queue_applied",
"role": "HA",
"status": "ONLINE",
"version": "8.0.33"
},
"mysqlu03:7306": {
"address": "mysqlu03:7306",
"memberRole": "SECONDARY",
"mode": "R/O",
"readReplicas": {},
"replicationLag": "applier_queue_applied",
"role": "HA",
"status": "ONLINE",
"version": "8.0.33"
}
},
"topologyMode": "Single-Primary"
},
"groupInformationSourceMember": "mysqlu01:7306"
}
MySQL 192.168.9.200:7306 ssl JS >
检查集群状态
最后再检查一次集群的状态
var cluster=dba.getCluster()
cluster.status();
MySQL Router安装
MySQL Router有两种配置方式，如下所示：
手工配置，手工填写后端 MGR 节点的地址，但是这样MySQL Router就没法感知 Primary 节点的变化，手工创建 MGR 时只能这么配置 引导模式自动进行配置,通过 mysql_innodb_cluster_metadata 元数据库动态感知 Primary 节点的变化,实现对应用的透明，这也是 InnoDB Cluster 的标准配置方法。
bootstrap模式
bootstrap模式支持failover，但是必须结合InnoDB Cluster使用，在--directory指定的路径下自动生成安装目录，配置文件里的端口为6446和6447
$ cd /data/soft
$ tar xvf mysql-router-8.0.35-linux-glibc2.28-x86_64.tar.xz -C /opt/mysql
$ cd /opt/mysql/
$ ln -s mysql-router-8.0.35-linux-glibc2.28-x86_64/ router
配置环境变量
#在mysql用户下编辑，加入下面配置信息
export PATH=$PATH:/opt/mysql/router/bin
执行下面命令，使之生效。
$ source ~/.bash_profile
#查看帮助信息
mysqlrouter --help
#创建目录
mkdir -p /data/mysqlrouter
初始化脚本(例子1)
mysqlrouter --bootstrap icadmin@mysqlu01:7306 --directory /data/mysqlrouter --name='icrouter' --force-password-validation
具体如下所示：
$ mysqlrouter --bootstrap icadmin@mysqlu01:7306 --directory /data/mysqlrouter --name='iicrouter' --force-password-validation
Please enter MySQL password for icadmin:
# Bootstrapping MySQL Router 8.0.35 (MySQL Community - GPL) instance at '/data/mysqlrouter'...
- Creating account(s) (only those that are needed, if any)
- Verifying account (using it to run SQL queries that would be run by Router)
- Storing account in keyring
- Adjusting permissions of generated files
- Creating configuration /data/mysqlrouter/mysqlrouter.conf
# MySQL Router 'iicrouter' configured for the ClusterSet 'yicticcset'
After this MySQL Router has been started with the generated configuration
$ mysqlrouter -c /data/mysqlrouter/mysqlrouter.conf
ClusterSet 'yicticcset' can be reached by connecting to:
## MySQL Classic protocol
- Read/Write Connections: localhost:6446
- Read/Only Connections: localhost:6447
## MySQL X protocol
- Read/Write Connections: localhost:6448
- Read/Only Connections: localhost:6449
初始化脚本(例子2)：
mysqlrouter --bootstrap icadmin@mysqlu01:7306 \
--directory /data/mysqlrouter \
--account iccrouter \
--user mysql --name icrouter \
--conf-bind-address="0.0.0.0" \
--account-host="192.168.9.%" --force-password-validation
注意：--conf-bind-address，如果想任何其它机器都能访问mysql router的话，那么--conf-bind-address应该设置为0.0.0.0，如果设置为某个IP，表示只能在这个IP访问mysql router，根据具体情况设置。
具体输出如下所示：
[mysql@mysqlu01 mysqlrouter]$ mysqlrouter --bootstrap icadmin@mysqlu01:7306 \
> --directory /data/mysqlrouter \
> --account iccrouter \
> --user mysql --name icrouter \
> --conf-bind-address="192.168.9.200" \
> --account-host="192.168.9.%" --force-password-validation
Please enter MySQL password for icadmin:
# Reconfiguring MySQL Router 8.0.35 (MySQL Community - GPL) instance at '/data/mysqlrouter'...
Please enter MySQL password for iccrouter:
- Creating account(s) (only those that are needed, if any)
- Using existing certificates from the '/data/mysqlrouter/data' directory
- Verifying account (using it to run SQL queries that would be run by Router)
- Storing account in keyring
- Adjusting permissions of generated files
- Creating configuration /data/mysqlrouter/mysqlrouter.conf
Existing configurations backed up to '/data/mysqlrouter/mysqlrouter.conf.bak'
# MySQL Router 'icrouter' configured for the InnoDB Cluster 'gsp_cluster'
After this MySQL Router has been started with the generated configuration
$ mysqlrouter -c /data/mysqlrouter/mysqlrouter.conf
InnoDB Cluster 'gsp_cluster' can be reached by connecting to:
## MySQL Classic protocol
- Read/Write Connections: localhost:6446
- Read/Only Connections: localhost:6447
## MySQL X protocol
- Read/Write Connections: localhost:6448
- Read/Only Connections: localhost:6449
[mysql@mysqlu01 mysqlrouter]$
查看MySQL Router信息
var cluster =dba.getCluster()
cluster.listRouters()
具体信息如下所示
配置MySQL Router的systemd服务，编辑配置/usr/lib/systemd/system/mysqlrouter.service
[Unit]
Description=MySQL Router
After=syslog.target
After=network.target
[Service]
Type=simple
User=mysql
Group=mysql
PIDFile=/data/mysqlrouter/mysqlrouter.pid
ExecStart=/opt/mysql/router/bin/mysqlrouter -c /data/mysqlrouter/mysqlrouter.conf
Restart=on-failure
PrivateTmp=true
[Install]
WantedBy=multi-user.target
然后执行下面命令
# systemctl daemon-reload
# systemctl enable mysqlrouter.service
# systemctl status mysqlrouter.service
# systemctl start mysqlrouter.service
启动MySQL Router后，可以通过下面命令查看/验证其监听端口是否开启。
$ netstat -ntlp |grep mysqlrouter
$ ps -ef | grep mysqlrouter | grep -v grep
然后依葫芦画瓢，在另外一台服务器上安装MySQL Router,关于MySQL Router的安装，一般应该在应用服务器或单独的服务器上安装MySQL Router，结合Keepalvied实现MySQL Router的高可用性，这里不做展开介绍。
