mysql innodb cluster 搭建

根據文檔搭建...https://dev.mysql.com/doc/refman/8.0/en/mysql-innodb-cluster-production-deployment.html

環境準備:
1 下載和安裝需要的軟件(本人的軟件版本--都是mysql Community中的Linux Generic版本)
mysql-server(mysql-8.0.17-linux-glibc2.12-x86_64.tar.xz)
mysql-router(mysql-router-8.0.17-linux-glibc2.12-x86_64.tar.xz)
mysql-shell(mysql-shell-8.0.17-linux-glibc2.12-x86-64bit.tar.gz)

安裝(以mysql server為例，其他類似,以下都是Mysql_tar操作系統用戶操作):
cd /home/mysql_tar
tar -xvf mysql-8.0.17-linux-glibc2.12-x86_64.tar.xz
ln -s mysql-8.0.17-linux-glibc2.12-x86_64 mysql_install(方便升級)
...mysql-router...
....mysql_shell...

2. 編輯環境變量:
   vim /home/mysql_tar/.bash_profile
   #FOR MYSQL
   MYSQL_HOME=/home/mysql_tar/mysql_install
   PATH=$PATH:$MYSQL_HOME/bin
   export MYSQL_HOME

#MYSQL SHELL
MYSQL_SHELL_HOME=/home/mysql_tar/mysql_shell
PATH=$PATH:$MYSQL_SHELL_HOME/bin
export MYSQL_SHELL_HOME

#MYSQL_ROUTER
MYSQL_ROUTER=/home/mysql_tar/mysql_router
PATH=$PATH:$MYSQL_ROUTER/bin
export MYSQL_ROUTER

export PATH

3. 準備mysql 配置文件my.cnf
   vim /etc/my.cnf

default-authentication-plugin=mysql_native_password
lower_case_table_names=1
datadir=/data_test
socket=/data_test/mysql.sock
log-error=/data_test/mysqld.log
pid-file=/data_test/mysqld.pid

4. 創建數據目錄文件/data_test(用戶和用戶組均為mysql_tar)
5. 初始化mysql
   cd /home/mysql_tar/mysql_install/bin(環境變量設置正確，該步可有可無)
   ./mysqld --initialize --user=mysql_tar(初始化mysql系統表空間和其他重要文件，initialize 拼錯的話不會報錯，只會提示數據目錄找不到)
6. 啟動Mysql
   mysqld_safe --user=mysql_tar &
7. 連接Mysql并且修改root賬戶密碼:
   ./mysql -u root -S /data_test/mysql.sock -p(也可以通過TCP/IP登陸，這里通過套接字登陸)
   mysql>alter user root@localhost identified by 'mjj';
8. 通過mysqlsh登陸mysql、檢查環境并創建集群
   /home/mysql_tar/mysql_shell/bin/mysqlsh
   MySQL SQL > \connect root@mysql_host_a(加粗的是我的命令)
   Creating a session to 'root@mysql_host_a'
   Please provide the password for 'root@mysql_host_a': *
   Save password for 'root@mysql_host_a'? [Y]es/[N]o/Ne[v]er (default No): ~~
   MySQL mysql_host_a:33060+ ssl JS > dba.checkInstanceConfiguration();
   Validating local MySQL instance listening at port 3306 for use in an InnoDB cluster...**

This instance reports its own address as mysql_host_a:3306
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...

NOTE: Some configuration options need to be fixed:
+--------------------------+---------------+----------------+--------------------------------------------------+
| Variable | Current Value | Required Value | Note |
+--------------------------+---------------+----------------+--------------------------------------------------+
| binlog_checksum | CRC32 | NONE | Update the server variable |
| enforce_gtid_consistency | OFF | ON | Update read-only variable and restart the server |
| gtid_mode | OFF | ON | Update read-only variable and restart the server |
| server_id | 1 | <unique ID> | Update read-only variable and restart the server |
+--------------------------+---------------+----------------+--------------------------------------------------+

Some variables need to be changed, but cannot be done dynamically on the server.
NOTE: Please use the dba.configureInstance() command to repair these issues.

{
"config_errors": [
{
"action": "server_update",
"current": "CRC32",
"option": "binlog_checksum",
"required": "NONE"
},
{
"action": "server_update+restart",
"current": "OFF",
"option": "enforce_gtid_consistency",
"required": "ON"
},
{
"action": "server_update+restart",
"current": "OFF",
"option": "gtid_mode",
"required": "ON"
},
{
"action": "server_update+restart",
"current": "1",
"option": "server_id",
"required": "<unique ID>"
}
],
"status": "error"
}
MySQL mysql_host_a:33060+ ssl JS > \exit
Bye!

根據錯誤往/etc/my.cnf添加以下參數:
#for innodb cluster
binlog_checksum=none
enforce_gtid_consistency=on
gtid_mode=on
server_id=1234

9. 創建集群
   MySQL mysql_host_a:33060+ ssl JS > var cluster = dba.createCluster('mjjcluster');
   A new InnoDB cluster will be created on instance 'mysql_host_a:3306'.

Validating instance at mysql_host_a:3306...

This instance reports its own address as mysql_host_a:3306

Instance configuration is suitable.
Creating InnoDB cluster 'mjjcluster' on 'mysql_host_a:3306'...

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.

10 可以通過cluster.status();命令查看集群狀態
MySQL mysql_host_a:33060+ ssl JS > cluster.status();
{
"clusterName": "mjjcluster",
"defaultReplicaSet": {
"name": "default",
"primary": "mysql_host_a:3306",
"ssl": "REQUIRED",
"status": "OK_NO_TOLERANCE",
"statusText": "Cluster is NOT tolerant to any failures.",
"topology": {
"mysql_host_a:3306": {
"address": "mysql_host_a:3306",
"mode": "R/W",
"readReplicas": {},
"role": "HA",
"status": "ONLINE",
"version": "8.0.17"
}
},
"topologyMode": "Single-Primary"
},
"groupInformationSourceMember": "mysql_host_a:3306"
}

11, 其他機子也安裝軟件和準備環境(dba.checkInstanceConfiguration()通過即可，步驟與主節點類似)

12. 加入節點:
    MySQL mysql_host_a:33060+ ssl JS > cluster.addInstance('root@mysql_host_b:3306');(本人另一臺機子的主機名是mysql_host_b)
    Cluster.addInstance: Connection 'root@mysql_host_b:3306' is not valid: unable to resolve the IPv4 address. (ArgumentError)
    MySQL mysql_host_a:33060+ ssl JS > cluster.addInstance('root@mysql_host_b:3306');
    Please provide the password for 'root@mysql_host_b:3306': ***
    Save password for 'root@mysql_host_b:3306'? [Y]es/[N]o/Ne[v]er (default No):

NOTE: The target instance 'mysql_host_b:3306' has not been pre-provisioned (GTID set
is empty). The Shell is unable to decide whether incremental distributed 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
'mysql_host_b:3306' with a physical snapshot from an existing cluster member.
To use this method by default, set the 'recoveryMethod' option to 'clone'.

The incremental distributed 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):
Validating instance at mysql_host_b:3306...

This instance reports its own address as mysql_host_b:3306

Instance configuration is suitable.
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: mysql_host_b:3306 is being cloned from mysql_host_a:3306
  Stage DROP DATA: Completed
  Clone Transfer
  FILE COPY ############################################################ 100% Completed
  PAGE COPY ############################################################ 100% Completed
  REDO COPY ############################################################ 100% Completed

NOTE: mysql_host_b:3306 is shutting down...

• Waiting for server restart... ready
• mysql_host_b:3306 has restarted, waiting for clone to finish...
  ** Stage RESTART: Completed
• Clone process has finished: 58.50 MB transferred in about 1 second (~inf TB/s)

State recovery already finished for 'mysql_host_b:3306'

The instance 'mysql_host_b:3306' was successfully added to the cluster.

。。。完成了，基本的步驟就這些吧。
主要方法:
dba.configureInstance()

dba.createCluster()

Cluster.addInstance()----cluster=dba.getCluster()獲取cluster變量

Cluster.removeInstance()

Cluster.rejoinInstance()