【Docker笔记03】【MySQL 与 Redis的主从安装】

一、前言

本系列是根据 B 站 尚硅谷 Docker 视频 学习记录笔记。因为没有视频课件，部分内容摘自 https://www.yuque.com/tmfl/cloud/dketq0。

本系列仅为自身学习笔记记录使用，记录存在偏差，推荐阅读原视频内容或本文参考笔记。

二、Mysql 安装

  1. 创建主服务容器实例（端口为 3307）

    [root@192 /]# docker run -d -p 3307:3306 --privileged=true -v /mydocker/mysql-master/log:/var/log/mysql -v /mydocker/mysql-master/data:/var/lib/mysql -v /mydocker/mysql-master/conf:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=root --name mysql-master  mysql:5.7
074c2c85947c79a139c6d8a938480de504f65c9f214171b125c34e19e99f14e6
[root@192 /]# docker ps
CONTAINER ID   IMAGE         COMMAND                   CREATED         STATUS         PORTS                                                  NAMES
074c2c85947c   mysql:5.7     "docker-entrypoint.s…"   4 seconds ago   Up 3 seconds   33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp   mysql-master

  2. 在 /mydocker/mysql-master/conf 目录下新建 my.cnf 并新增如下内容

    [root@192 conf]# vim my.cnf
[root@192 conf]# cat my.cnf 
[mysqld]
## 设置server_id, 同一个局域网中需要唯一
server_id=101
## 指定不需要同步的数据库名称
binlog-ignore-db=mysql
## 开启二进制日志功能
log-bin=mall-mysql-bin
## 设置二进制日志使用内存大小（事务）
binlog_cache_size=1M
## 设置使用的二进制日志格式（mixed,statement,row）
binlog_format=mixed
## 二进制日志过期清理时间。默认值为0，表示不自动清理
expire_logs_days=7
## 跳过主从复制中遇到的所有错误或指定类型的错误，避免slave端复制中断
## 如：1062错误是指一些主键重复，1032错误是因为主从数据库数据不一致
slave_skip_errors=1062

  3. 重启 mysql-master 实例

    [root@192 conf]# docker restart mysql-master 
mysql-master
[root@192 conf]# docker ps
CONTAINER ID   IMAGE       COMMAND                   CREATED         STATUS         PORTS                                                  NAMES
074c2c85947c   mysql:5.7   "docker-entrypoint.s…"   8 minutes ago   Up 2 seconds   33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp   mysql-master

  4. 连接 mysql-master 创建主从同步用户

    # 进入
[root@192 conf]#  docker exec -it mysql-master  /bin/bash
# 登录 mysql
root@074c2c85947c:/# mysql -uroot -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 2
Server version: 5.7.36-log MySQL Community Server (GPL)Copyright (c) 2000, 2021, Oracle and/or its affiliates.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.
# 创建 slave 用户，密码 123456	
mysql> create user 'slave'@'%' identified by '123456';
Query OK, 0 rows affected (0.01 sec)
# 对 slave 用户进行授权
mysql> grant replication slave, replication client on *.* to 'slave'@'%';
Query OK, 0 rows affected (0.00 sec)mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

  5. 创建从服务器（端口为 3308）

    [root@192 conf]# docker run -d -p 3308:3306 --privileged=true -v /mydocker/mysql-slave/log:/var/log/mysql -v /mydocker/mysql-slave/data:/var/lib/mysql -v /mydocker/mysql-slave/conf:/etc/mysql/conf.d -e MYSQL_ROOT_PASSWORD=root --name mysql-slave  mysql:5.7
0401aa0491f475635e66a1535479b68ab60ec558229df4adbebe66dc95d1e387
[root@192 conf]# docker ps
CONTAINER ID   IMAGE       COMMAND                   CREATED          STATUS         PORTS                                                  NAMES
0401aa0491f4   mysql:5.7   "docker-entrypoint.s…"   3 seconds ago    Up 2 seconds   33060/tcp, 0.0.0.0:3308->3306/tcp, :::3308->3306/tcp   mysql-slave
074c2c85947c   mysql:5.7   "docker-entrypoint.s…"   14 minutes ago   Up 6 minutes   33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp   mysql-master

  6. 在 /mydocker/mysql-slave/conf 目录下新建 my.cnf 并新增如下内容

    [root@192 conf]# vim my.cnf
[root@192 conf]# cat my.cnf 
[mysqld]
## 设置server_id, 同一个局域网内需要唯一
server_id=102
## 指定不需要同步的数据库名称
binlog-ignore-db=mysql
## 开启二进制日志功能，以备slave作为其它数据库实例的Master时使用
log-bin=mall-mysql-slave1-bin
## 设置二进制日志使用内存大小（事务）
binlog_cache_size=1M
## 设置使用的二进制日志格式（mixed,statement,row）
binlog_format=mixed
## 二进制日志过期清理时间。默认值为0，表示不自动清理
expire_logs_days=7
## 跳过主从复制中遇到的所有错误或指定类型的错误，避免slave端复制中断
## 如：1062错误是指一些主键重复，1032是因为主从数据库数据不一致
slave_skip_errors=1062
## relay_log配置中继日志
relay_log=mall-mysql-relay-bin
## log_slave_updates表示slave将复制事件写进自己的二进制日志
log_slave_updates=1
## slave设置只读（具有super权限的用户除外）
read_only=1

  7. 重启 slave 容器

    [root@192 mysql-slave]# docker restart mysql-slave 
mysql-slave
[root@192 mysql-slave]# docker ps
CONTAINER ID   IMAGE       COMMAND                   CREATED          STATUS          PORTS                                                  NAMES
0401aa0491f4   mysql:5.7   "docker-entrypoint.s…"   3 minutes ago    Up 29 seconds   33060/tcp, 0.0.0.0:3308->3306/tcp, :::3308->3306/tcp   mysql-slave
074c2c85947c   mysql:5.7   "docker-entrypoint.s…"   17 minutes ago   Up 9 minutes    33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp   mysql-master

  8. 在主服务器中查看主从同步状态 （show master status; 命令）

    [root@192 mysql-slave]# docker exec -it mysql-master /bin/bash
root@074c2c85947c:/# mysql -uroot -p
Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3
Server version: 5.7.36-log MySQL Community Server (GPL)Copyright (c) 2000, 2021, Oracle and/or its affiliates.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> show master status;
+-----------------------+----------+--------------+------------------+-------------------+
| File                  | Position | Binlog_Do_DB | Binlog_Ignore_DB | Executed_Gtid_Set |
+-----------------------+----------+--------------+------------------+-------------------+
| mall-mysql-bin.000001 |      769 |              | mysql            |                   |
+-----------------------+----------+--------------+------------------+-------------------+
1 row in set (0.00 sec)

  9. 进入 slave 服务器，配置主从复制关系

    # 格式：
# change master to master_host='宿主机ip',master_user='主数据库配置的主从复制用户名',master_password='主数据库配置的主从复制用户密码',master_port=宿主机主数据库端口,master_log_file='主数据库主从同步状态的文件名File',master_log_pos=主数据库主从同步状态的Position,master_connect_retry=连接失败重试时间间隔（秒）;
mysql> change master to master_host='192.168.64.132',master_user='slave',master_password='123456',master_port=3307,master_log_file='mall-mysql-bin.000001',master_log_pos=769,master_connect_retry=30;
Query OK, 0 rows affected, 2 warnings (0.01 sec)
mysql> 
# 查看主从同步关系 （或使用 show slave status \G; 命令查看key value 格式）
mysql> show slave status;
+----------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+-------------+----------------------------+-----------+---------------------+-------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
| Slave_IO_State | Master_Host    | Master_User | Master_Port | Connect_Retry | Master_Log_File       | Read_Master_Log_Pos | Relay_Log_File              | Relay_Log_Pos | Relay_Master_Log_File | Slave_IO_Running | Slave_SQL_Running | Replicate_Do_DB | Replicate_Ignore_DB | Replicate_Do_Table | Replicate_Ignore_Table | Replicate_Wild_Do_Table | Replicate_Wild_Ignore_Table | Last_Errno | Last_Error | Skip_Counter | Exec_Master_Log_Pos | Relay_Log_Space | Until_Condition | Until_Log_File | Until_Log_Pos | Master_SSL_Allowed | Master_SSL_CA_File | Master_SSL_CA_Path | Master_SSL_Cert | Master_SSL_Cipher | Master_SSL_Key | Seconds_Behind_Master | Master_SSL_Verify_Server_Cert | Last_IO_Errno | Last_IO_Error | Last_SQL_Errno | Last_SQL_Error | Replicate_Ignore_Server_Ids | Master_Server_Id | Master_UUID | Master_Info_File           | SQL_Delay | SQL_Remaining_Delay | Slave_SQL_Running_State | Master_Retry_Count | Master_Bind | Last_IO_Error_Timestamp | Last_SQL_Error_Timestamp | Master_SSL_Crl | Master_SSL_Crlpath | Retrieved_Gtid_Set | Executed_Gtid_Set | Auto_Position | Replicate_Rewrite_DB | Channel_Name | Master_TLS_Version |
+----------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+-------------+----------------------------+-----------+---------------------+-------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
|                | 192.168.64.132 | slave       |        3307 |            30 | mall-mysql-bin.000001 |                 769 | mall-mysql-relay-bin.000001 |             4 | mall-mysql-bin.000001 | No               | No                |                 |                     |                    |                        |                         |                             |          0 |            |            0 |                 769 |             154 | None            |                |             0 | No                 |                    |                    |                 |                   |                |                  NULL | No                            |             0 |               |              0 |                |                             |                0 |             | /var/lib/mysql/master.info |         0 |                NULL |                         |              86400 |             |                         |                          |                |                    |                    |                   |             0 |                      |              |                    |
+----------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+-------------+----------------------------+-----------+---------------------+-------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
1 row in set (0.00 sec)

    其中看到参数 Slave_IO_Running 和 Slave_SQL_Running 两个复制线程都还没有开始

  10. 在从数据库中开启主从同步

    # 开启主从同步
mysql> start slave;
Query OK, 0 rows affected (0.00 sec)
# 查看 Slave_IO_Running 和 Slave_SQL_Running 已经开启主从同步  
mysql> show slave status;
+----------------------------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+--------------------------------------+----------------------------+-----------+---------------------+--------------------------------------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
| Slave_IO_State                   | Master_Host    | Master_User | Master_Port | Connect_Retry | Master_Log_File       | Read_Master_Log_Pos | Relay_Log_File              | Relay_Log_Pos | Relay_Master_Log_File | Slave_IO_Running | Slave_SQL_Running | Replicate_Do_DB | Replicate_Ignore_DB | Replicate_Do_Table | Replicate_Ignore_Table | Replicate_Wild_Do_Table | Replicate_Wild_Ignore_Table | Last_Errno | Last_Error | Skip_Counter | Exec_Master_Log_Pos | Relay_Log_Space | Until_Condition | Until_Log_File | Until_Log_Pos | Master_SSL_Allowed | Master_SSL_CA_File | Master_SSL_CA_Path | Master_SSL_Cert | Master_SSL_Cipher | Master_SSL_Key | Seconds_Behind_Master | Master_SSL_Verify_Server_Cert | Last_IO_Errno | Last_IO_Error | Last_SQL_Errno | Last_SQL_Error | Replicate_Ignore_Server_Ids | Master_Server_Id | Master_UUID                          | Master_Info_File           | SQL_Delay | SQL_Remaining_Delay | Slave_SQL_Running_State                                | Master_Retry_Count | Master_Bind | Last_IO_Error_Timestamp | Last_SQL_Error_Timestamp | Master_SSL_Crl | Master_SSL_Crlpath | Retrieved_Gtid_Set | Executed_Gtid_Set | Auto_Position | Replicate_Rewrite_DB | Channel_Name | Master_TLS_Version |
+----------------------------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+--------------------------------------+----------------------------+-----------+---------------------+--------------------------------------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
| Waiting for master to send event | 192.168.64.132 | slave       |        3307 |            30 | mall-mysql-bin.000001 |                 769 | mall-mysql-relay-bin.000002 |           325 | mall-mysql-bin.000001 | Yes              | Yes               |                 |                     |                    |                        |                         |                             |          0 |            |            0 |                 769 |             537 | None            |                |             0 | No                 |                    |                    |                 |                   |                |                     0 | No                            |             0 |               |              0 |                |                             |              101 | a382dfa8-e507-11ee-9375-0242ac110004 | /var/lib/mysql/master.info |         0 |                NULL | Slave has read all relay log; waiting for more updates |              86400 |             |                         |                          |                |                    |                    |                   |             0 |                      |              |                    |
+----------------------------------+----------------+-------------+-------------+---------------+-----------------------+---------------------+-----------------------------+---------------+-----------------------+------------------+-------------------+-----------------+---------------------+--------------------+------------------------+-------------------------+-----------------------------+------------+------------+--------------+---------------------+-----------------+-----------------+----------------+---------------+--------------------+--------------------+--------------------+-----------------+-------------------+----------------+-----------------------+-------------------------------+---------------+---------------+----------------+----------------+-----------------------------+------------------+--------------------------------------+----------------------------+-----------+---------------------+--------------------------------------------------------+--------------------+-------------+-------------------------+--------------------------+----------------+--------------------+--------------------+-------------------+---------------+----------------------+--------------+--------------------+
1 row in set (0.01 sec)

  11. 验证 主从同步，可以通过命令或客户端验证，这里不再展示。

三、Redis 安装

1. Redis 三主三从

  1. 搭建六台 Redis 节点

    # 启动6台Redis节点
# --net host 使用宿主机的IP和端口，默认
# --cluster-enabled yes 开启redis集群
# --appendonly yes 开启redis持久化
# --port 6381 配置redis端口号
[root@192 ~]# docker run -d --name redis-node-1 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-1:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6381
[root@192 ~]# docker run -d --name redis-node-2 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-2:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6382
ca49edab5c26631b0e35a40ed460a1a8a00f9c3ff74f58c9267dc52b62abfeab
[root@192 ~]# docker run -d --name redis-node-3 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-3:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6383
72932ccc332432d0dd3a7e5b129c0d80d3be53bfb031894ac392460bf1c4a9d2
[root@192 ~]# docker run -d --name redis-node-4 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-4:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6384
461cb9285bda92e8f0e87a3f087b17e421068b12d857e8699d676acaa168d25e
[root@192 ~]# docker run -d --name redis-node-5 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-5:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6385
c13f90d780d4c21e9b7f7c9af8d2fafd62f1f22baa7ec1e8d6cffdaaf707c9c2
[root@192 ~]# docker run -d --name redis-node-6 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-6:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6386
6b81a9d791a78cb37358383580041016441523c452f45f081367658e61591e06
[root@192 ~]# docker ps
CONTAINER ID   IMAGE         COMMAND                   CREATED             STATUS             PORTS                                                  NAMES
6b81a9d791a7   redis:6.0.8   "docker-entrypoint.s…"   6 seconds ago       Up 6 seconds                                                              redis-node-6
c13f90d780d4   redis:6.0.8   "docker-entrypoint.s…"   12 seconds ago      Up 12 seconds                                                             redis-node-5
461cb9285bda   redis:6.0.8   "docker-entrypoint.s…"   19 seconds ago      Up 19 seconds                                                             redis-node-4
72932ccc3324   redis:6.0.8   "docker-entrypoint.s…"   24 seconds ago      Up 24 seconds                                                             redis-node-3
ca49edab5c26   redis:6.0.8   "docker-entrypoint.s…"   33 seconds ago      Up 33 seconds                                                             redis-node-2
ab397ce2f7f0   redis:6.0.8   "docker-entrypoint.s…"   5 minutes ago       Up 5 minutes                                                              redis-node-1
0401aa0491f4   mysql:5.7     "docker-entrypoint.s…"   53 minutes ago      Up 51 minutes      33060/tcp, 0.0.0.0:3308->3306/tcp, :::3308->3306/tcp   mysql-slave
074c2c85947c   mysql:5.7     "docker-entrypoint.s…"   About an hour ago   Up About an hour   33060/tcp, 0.0.0.0:3307->3306/tcp, :::3307->3306/tcp   mysql-master
[root@192 ~]#

  2. 任选一台 Redis 主机，构建主从关系

    # 进入一台Redis集群服务
[root@192 etc]# docker exec -it redis-node-1 /bin/bash
# 执行主从构建命令.可以从日志中看到打印的Redis 槽的指派信息
root@192:/data# redis-cli --cluster create 192.168.64.132:6381 192.168.64.132:6382 192.168.64.132:6383 192.168.64.132:6384 192.168.64.132:6385 192.168.64.132:6386 --cluster-replicas 1
>>> Performing hash slots allocation on 6 nodes...
Master[0] -> Slots 0 - 5460
Master[1] -> Slots 5461 - 10922
Master[2] -> Slots 10923 - 16383
Adding replica 192.168.64.132:6385 to 192.168.64.132:6381
Adding replica 192.168.64.132:6386 to 192.168.64.132:6382
Adding replica 192.168.64.132:6384 to 192.168.64.132:6383
>>> Trying to optimize slaves allocation for anti-affinity
[WARNING] Some slaves are in the same host as their master
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-5460] (5461 slots) master
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[5461-10922] (5462 slots) master
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[10923-16383] (5461 slots) master
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384replicates 6455206ef6ce922ced57adf10f05d58d7d46125d
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385replicates 4e378a4800f20ff6fb36c833310a19041d70c905
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386replicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Assign a different config epoch to each node
>>> Sending CLUSTER MEET messages to join the cluster
Waiting for the cluster to join
.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-5460] (5461 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[5461-10922] (5462 slots) master1 additional replica(s)
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[10923-16383] (5461 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

  3. 查看集群状态

    # 进入一个 Redis 节点，通过 cluster info 命令查看集群状态
root@192:/data# redis-cli -p 6381
127.0.0.1:6381> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:1
cluster_stats_messages_ping_sent:656
cluster_stats_messages_pong_sent:699
cluster_stats_messages_sent:1355
cluster_stats_messages_ping_received:694
cluster_stats_messages_pong_received:656
cluster_stats_messages_meet_received:5
cluster_stats_messages_received:1355# 查看集群节点信息
127.0.0.1:6381> cluster nodes
c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385@16385 slave 4e378a4800f20ff6fb36c833310a19041d70c905 0 1710763297834 1 connected
9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382@16382 master - 0 1710763296827 2 connected 5461-10922
0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384@16384 slave 6455206ef6ce922ced57adf10f05d58d7d46125d 0 1710763296000 3 connected
6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383@16383 master - 0 1710763297000 3 connected 10923-16383
89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386@16386 slave 9efa8469bdd5450dd38453d5b7f8b28e619ca147 0 1710763296000 2 connected
# 当前节点编号是 4e378a4800f20ff6fb36c833310a19041d70c905, c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 是 当前节点的从节点，即 6381 的从节点是 6385
4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381@16381 myself,master - 0 1710763297000 1 connected 0-5460

  4. 集群模式连接 Redis （redis-cli -p 端口 -c）

    # 集群模式连接 Redis, 加 -c 代表  cluster 
root@192:/data# redis-cli -p 6381 -c
# set key 值会计算出所属的Redis 槽，然后路由过去
127.0.0.1:6381> set k1 v1
-> Redirected to slot [12706] located at 192.168.64.132:6383
OK
192.168.64.132:6383> set k2 v2
-> Redirected to slot [449] located at 192.168.64.132:6381
OK
192.168.64.132:6381> set k3 k3
OK
192.168.64.132:6381> get k1
-> Redirected to slot [12706] located at 192.168.64.132:6383
"v1"

  5. 查看集群信息 (cluster check)

    # 通过 --cluster check 可以检测集群情况
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 2 keys | 5461 slots | 1 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 5462 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 5461 slots | 1 slaves.
[OK] 3 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-5460] (5461 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[5461-10922] (5462 slots) master1 additional replica(s)
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[10923-16383] (5461 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

补充：

  1. 默认情况下Redis 集群主节点下线后，从节点会变成主节点。
  2. Redis 集群三主三从中如果同一主从都掉线，Redis 集群处于下线状态，即使可以连接某个节点也是无法操作任何数据。
    # 停止到6381 和 其从节点 6385 后，集群处于掉线状态，
[root@192 etc]# docker exec -it redis-node-2 /bin/bash
# 连接 6382 节点但是无法操作数据
root@192:/data# redis-cli -p 6382 -c
127.0.0.1:6382> get k1
(error) CLUSTERDOWN The cluster is down
127.0.0.1:6382> set k5 v5
(error) CLUSTERDOWN The cluster is down
# 查看集群状态处于 fail状态
127.0.0.1:6382> cluster info
cluster_state:fail
cluster_slots_assigned:16384
cluster_slots_ok:10923
cluster_slots_pfail:0
cluster_slots_fail:5461
cluster_known_nodes:6
cluster_size:3
cluster_current_epoch:6
cluster_my_epoch:2
cluster_stats_messages_ping_sent:2561
cluster_stats_messages_pong_sent:2564
cluster_stats_messages_meet_sent:1
cluster_stats_messages_fail_sent:3
cluster_stats_messages_sent:5129
cluster_stats_messages_ping_received:2564
cluster_stats_messages_pong_received:2560
cluster_stats_messages_fail_received:2
cluster_stats_messages_received:5126

2. Redis 扩容和缩容

2.1 扩容

扩容为四主四从：

  1. 创建新的Redis节点 6387 和 6388

    [root@192 etc]# docker run -d --name redis-node-7 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-7:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6387
8735fe90539868853389975bf135a94833853c66552cd0a175f626fcf81a7e86
[root@192 etc]# docker run -d --name redis-node-8 --net host --privileged=true -v /mydocker/redis-cluster/share/redis-node-8:/data redis:6.0.8 --cluster-enabled yes --appendonly yes --port 6388
4b88401a4f27e257197c46913c2f49c18e0e49f6bfd31d515f6e0f0628394b8c

  2. 将 6387 节点作为主节点加入到集群中

    # 进入 6387 节点
[root@192 etc]# docker exec -it redis-node-7 /bin/bash
# redis-cli --cluster add-node 本节点地址 要加入的集群中的其中一个节点地址
root@192:/data# redis-cli --cluster add-node 192.168.64.132:6387 192.168.64.132:6381
>>> Adding node 192.168.64.132:6387 to cluster 192.168.64.132:6381
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-5460] (5461 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[5461-10922] (5462 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[10923-16383] (5461 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.64.132:6387 to make it join the cluster.
[OK] New node added correctly.# 节点检测可以看到 6387 已经加入集群并作为一个主节点
# 但是需要注意这里并没有给6387节点分配槽信息
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 2 keys | 5461 slots | 1 slaves.
192.168.64.132:6387 (827e12ca...) -> 0 keys | 0 slots | 0 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 5462 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 5461 slots | 1 slaves.
[OK] 3 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-5460] (5461 slots) master1 additional replica(s)
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots: (0 slots) master
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[5461-10922] (5462 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[10923-16383] (5461 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

  3. 对集群进行槽位重分配

    # redis经过槽位检查后，会提示需要分配的槽位数量： 
# 例如，我们现在是4台master，我们想要给node7分配4096个槽位，这样每个节点都是4096个槽位。
# 输入4096后，会让输入要接收这些哈希槽的节点ID，填入node7的节点ID即可。（就是节点信息中很长的一串十六进制串）。
# 然后会提示，询问要从哪些节点中拨出一部分槽位凑足4096个分给Node7。一般选择 all，即将之前的3个主节点的槽位都均一些给Node7，这样可以使得每个节点的槽位数相等均衡。
# 输入all之后，redis会列出一个计划，内容是自动从前面的3台master中拨出一部分槽位分给Node7的槽位，需要确认一下分配的计划。
# 输入yes确认后，redis便会自动重新洗牌，给Node7分配槽位。 
root@192:/data# redis-cli --cluster reshard 192.168.64.132:6381
# 询问想要重新分配几个槽位
How many slots do you want to move (from 1 to 16384)? 4096
# 询问哪个节点接受这些槽信息
What is the receiving node ID? 827e12cac658b16653c3d5028ba414b0b4390414 
Please enter all the source node IDs.
Type 'all' to use all the nodes as source nodes for the hash slots.
Type 'done' once you entered all the source nodes IDs.
# 选择all
Source node #1: all
...# 重新分配后可以通过如下命令查看分配结果
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 1 keys | 4096 slots | 1 slaves.
192.168.64.132:6387 (827e12ca...) -> 1 keys | 4096 slots | 0 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 4096 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 4096 slots | 1 slaves.
[OK] 3 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[1365-5460] (4096 slots) master1 additional replica(s)
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

    这里需要注意的是：重新分配后槽位并非是完全重新分配的，因为对于之前的节点槽位来说，完全重新分配代价太大，涉及大量数据迁移，因此这里会将之前节点的部分槽位分配给新的节点。如下：

    节点1：[1365-5460]（供4096个槽位），，，分配前为[0-5460]（共5461个槽位）
节点2：[6827-10922]（共4096个槽位），，，分配前为[5461-10922]（共5461个槽位）
节点3：[12288-16383]（共4096个槽位），，，分配前为[10923-16383]（共5462个槽位）节点7：[0-1364],[5461-6826],[10923-12287]（共4096个槽位），从每个节点中匀出来了一部分给了节点7

  4. 为主节点 6387 分配从节点 6388

    # redis-cli --cluster add-node 192.168.xxx.xxx:6388 192.168.xxx.xxx:6381 --cluster-slave --cluster-master-id node7节点的十六进制编号字符串
root@192:/data# redis-cli --cluster add-node 192.168.64.132:6388 192.168.64.132:6381 --cluster-slave --cluster-master-id 827e12cac658b16653c3d5028ba414b0b4390414
>>> Adding node 192.168.64.132:6388 to cluster 192.168.64.132:6381
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[1365-5460] (4096 slots) master1 additional replica(s)
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.64.132:6388 to make it join the cluster.
Waiting for the cluster to join>>> Configure node as replica of 192.168.64.132:6387.
[OK] New node added correctly.
# 查看集群状态
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 1 keys | 4096 slots | 1 slaves.
192.168.64.132:6387 (827e12ca...) -> 1 keys | 4096 slots | 1 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 4096 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 4096 slots | 1 slaves.
[OK] 3 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[1365-5460] (4096 slots) master1 additional replica(s)
S: 62c616c6fac267a8c8d0dcf122b4e28ec0a4728c 192.168.64.132:6388slots: (0 slots) slavereplicates 827e12cac658b16653c3d5028ba414b0b4390414
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

2.2 主从缩容

将四主四从缩容为三主三从

  1. 删除 6388 节点

    # 获取节点状态
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 1 keys | 4096 slots | 1 slaves.
192.168.64.132:6387 (827e12ca...) -> 1 keys | 4096 slots | 1 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 4096 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 4096 slots | 1 slaves.
[OK] 3 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[1365-5460] (4096 slots) master1 additional replica(s)
S: 62c616c6fac267a8c8d0dcf122b4e28ec0a4728c 192.168.64.132:6388slots: (0 slots) slavereplicates 827e12cac658b16653c3d5028ba414b0b4390414
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots:[0-1364],[5461-6826],[10923-12287] (4096 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
# 移除 6388 节点
root@192:/data# redis-cli --cluster del-node 192.168.64.132:6388 62c616c6fac267a8c8d0dcf122b4e28ec0a4728c
>>> Removing node 62c616c6fac267a8c8d0dcf122b4e28ec0a4728c from cluster 192.168.64.132:6388
>>> Sending CLUSTER FORGET messages to the cluster...
>>> Sending CLUSTER RESET SOFT to the deleted node.

  2. 对 6387 节点进行槽位重分配

    # 对整个集群进行重新分片
redis-cli --cluster reshard 192.168.64.132:6381
...
# Redis经过槽位检查后，会提示需要分配的槽位数量： 
# 如果我们想直接把node7的4096个哈希槽全部分给某个节点，可以直接输入4096。
# 输入4096后，会让输入要接收这些哈希槽的节点ID。假如我们想把这4096个槽都分给Node1，直接输入node1节点的编号即可。
# 然后会提示，询问要从哪些节点中拨出一部分槽位凑足4096个分给Node1。这里我们输入node7的节点编号，回车后输入done。 # 需要重新分配多少个节点
How many slots do you want to move (from 1 to 16384)? 4096
# 哪个节点接收这些槽位，这里选择节点1
What is the receiving node ID? 4e378a4800f20ff6fb36c833310a19041d70c905
# 选择这些槽位从那些节点划出用来分配给节点1
Please enter all the source node IDs.Type 'all' to use all the nodes as source nodes for the hash slots.Type 'done' once you entered all the source nodes IDs.
# 选择节点7来划出槽位供分配
Source node #1: 827e12cac658b16653c3d5028ba414b0b4390414
Source node #2: done# 查看集群状态
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 2 keys | 8192 slots | 1 slaves.
# 6387 节点已经没有槽位了
192.168.64.132:6387 (827e12ca...) -> 0 keys | 0 slots | 0 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 4096 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 4096 slots | 1 slaves.
[OK] 3 keys in 4 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-6826],[10923-12287] (8192 slots) master1 additional replica(s)
M: 827e12cac658b16653c3d5028ba414b0b4390414 192.168.64.132:6387slots: (0 slots) master
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.# 删除 6387 节点
root@192:/data# redis-cli --cluster del-node 192.168.64.132:6387 827e12cac658b16653c3d5028ba414b0b4390414
>>> Removing node 827e12cac658b16653c3d5028ba414b0b4390414 from cluster 192.168.64.132:6387
>>> Sending CLUSTER FORGET messages to the cluster...
>>> Sending CLUSTER RESET SOFT to the deleted node.# 检查集群状态
root@192:/data# redis-cli --cluster check 192.168.64.132:6381
192.168.64.132:6381 (4e378a48...) -> 2 keys | 8192 slots | 1 slaves.
192.168.64.132:6382 (9efa8469...) -> 0 keys | 4096 slots | 1 slaves.
192.168.64.132:6383 (6455206e...) -> 1 keys | 4096 slots | 1 slaves.
[OK] 3 keys in 3 masters.
0.00 keys per slot on average.
>>> Performing Cluster Check (using node 192.168.64.132:6381)
M: 4e378a4800f20ff6fb36c833310a19041d70c905 192.168.64.132:6381slots:[0-6826],[10923-12287] (8192 slots) master1 additional replica(s)
S: c970d5d73d9b1aa7a2f1d1d06779e3b8856673ae 192.168.64.132:6385slots: (0 slots) slavereplicates 4e378a4800f20ff6fb36c833310a19041d70c905
M: 9efa8469bdd5450dd38453d5b7f8b28e619ca147 192.168.64.132:6382slots:[6827-10922] (4096 slots) master1 additional replica(s)
M: 6455206ef6ce922ced57adf10f05d58d7d46125d 192.168.64.132:6383slots:[12288-16383] (4096 slots) master1 additional replica(s)
S: 89ac15e265ee54982059e546d4c5db3ba460790e 192.168.64.132:6386slots: (0 slots) slavereplicates 9efa8469bdd5450dd38453d5b7f8b28e619ca147
S: 0f172b39151a1917ecab8d57a52ca7d3403d3616 192.168.64.132:6384slots: (0 slots) slavereplicates 6455206ef6ce922ced57adf10f05d58d7d46125d
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

四、参考内容

B 站 尚硅谷 Docker 视频
https://www.yuque.com/tmfl/cloud/dketq0

本文来自互联网用户投稿，该文观点仅代表作者本人，不代表本站立场。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如若转载，请注明出处：http://www.mzph.cn/news/793647.shtml

如若内容造成侵权/违法违规/事实不符，请联系多彩编程网进行投诉反馈email:809451989@qq.com，一经查实，立即删除！

相关文章

如何加速Docker镜像的构建过程？

如何加速Docker镜像的构建过程？

要加速Docker镜像的构建过程，你可以考虑以下几种方法： 使用多阶段构建：多阶段构建可以帮助你减少镜像的大小，从而加速构建过程。你可以将构建过程分为多个阶段，每个阶段只保留必要的文件和依赖，最终构建出一…
阅读更多...
10-用PySpark建立第一个Spark RDD

10-用PySpark建立第一个Spark RDD

目录 RDD概念RDD特点建立RDD的方式不同工具建立RDD的方式使用PySpark Shell(交互环境)建立RDD使用VSCode编程建立RDD使用Jupyter Notebook建立RDD 总结 PySpark实战笔记系列第一篇 RDD概念 Apache Spark的核心组件的基础是RDD。所谓的RDD，即弹性分布式数据集&#…
阅读更多...
Linux 关闭防火墙命令（新手）

Linux 关闭防火墙命令（新手）

关闭防火墙 查看防火墙状态 systemctl status firewalld.service 临时关闭防火墙（重启失效） systemctl stop firewalld.service 永久关闭防火墙 systemctl disable firewalld.servicesudo systemctl enable firewalld，这种方式输入命令…
阅读更多...
施耐德 Unity Pro PLC 编程软件介绍

施耐德 Unity Pro PLC 编程软件介绍

Unity Pro 软件基本介绍 Unity Pro 是施耐德中大型 PLC 的编程软件&#xff08;<–> 对应西门子 Step7&#xff09; 支持的 PLC&#xff1a;施耐德中大型 PLC 中型 PLC&#xff1a;Premium、M340&#xff08;<–> 对应西门子 S7-300、S7-1200&#xff09;大型 PL…
阅读更多...
【C++】探索C++中的类与对象（上）

【C++】探索C++中的类与对象（上）

​​ &#x1f331;博客主页&#xff1a;青竹雾色间. &#x1f618;博客制作不易欢迎各位&#x1f44d;点赞⭐收藏➕关注 ✨人生如寄&#xff0c;多忧何为 ✨ C是一种强大的编程语言&#xff0c;其面向对象的特性使得代码结构更加清晰、易于维护和扩展。在C中&#xff0c;类与…
阅读更多...
常见docker使用命令

常见docker使用命令

#搭建镜像 “”" sudo docker build -t es_refresh:V1.20230303 . “”" #启动容器 “”" docker run -d --namepara_classify -v /etc/localtime:/etc/localtime -v /data/chenhw/multi_label_classification:/edb2vec -p 8066:8066 --gpus ‘“device0”’…
阅读更多...
Day83：服务攻防-开发组件安全JacksonFastJson各版本XStreamCVE环境复现

Day83：服务攻防-开发组件安全JacksonFastJson各版本XStreamCVE环境复现

目录 J2EE-组件Jackson-本地demo&CVE 代码执行 (CVE-2020-8840) 代码执行 (CVE-2020-35728&#xff09; J2EE-组件FastJson-本地demo&CVE FastJson < 1.2.24 FastJson < 1.2.47 FastJson < 1.2.80 (利用条件比较苛刻) J2EE-组件XStream-靶场&CVE …
阅读更多...
高度不同的流体瀑布css实现方法

高度不同的流体瀑布css实现方法

商城商品列表 实现瀑布流展示&#xff0c;通过flex或grid实现会导致每行中的列高度一致&#xff0c;无法达到错落有致的感觉&#xff1b; 为此需要用到&#xff1a; CSS columns 属性 columns 属性是一个简写属性&#xff0c;用于设置列宽和列数。 CSS 语法 columns: column-wi…
阅读更多...
如何让Webots支持C#语言开发的控制器

如何让Webots支持C#语言开发的控制器

Webots支持C、C、Java、Python、Matlab这五种语言开发控制器&#xff0c;没有直接支持C#&#xff0c;但有个同事已经用C#写了大量的机器人控制代码&#xff0c;想在不把C#代码改写成C的情况下&#xff0c;直接用webots仿真&#xff0c;那就得想想办法。(不过&#xff0c;让Chat…
阅读更多...
字节新作：图像生成质量超越DiT

字节新作：图像生成质量超越DiT

&#x1f31f;每日更新最新高质量论文&#xff0c;关注我&#xff0c;时刻关注最新大模型进展。&#x1f31f; &#x1f4cc; 元数据概览&#xff1a; 标题&#xff1a;Visual Autoregressive Modeling: Scalable Image Generation via Next-Scale Prediction作者&#xff1a…
阅读更多...
Java 内存占用过高应该如何优化

Java 内存占用过高应该如何优化

优化Java程序的内存占用是提高程序性能和稳定性的重要任务之一。内存占用过高可能导致系统性能下降、内存泄漏、频繁的垃圾回收等问题&#xff0c;影响程序的运行效率和用户体验。因此&#xff0c;对于Java程序内存占用过高的情况&#xff0c;需要采取一系列措施进行优化。 1.…
阅读更多...
算法设计与分析实验报告java实现(排序算法、三壶谜题、交替放置的碟子、带锁的门)

算法设计与分析实验报告java实现(排序算法、三壶谜题、交替放置的碟子、带锁的门)

一、 实验目的 1&#xff0e;加深学生对算法设计方法的基本思想、基本步骤、基本方法的理解与掌握&#xff1b; 2&#xff0e;提高学生利用课堂所学知识解决实际问题的能力&#xff1b; 3&#xff0e;提高学生综合应用所学知识解决实际问题的能力。 二、实验任务 1、排序算法…
阅读更多...
【随笔】Git 高级篇 -- 相对引用2（十三）

【随笔】Git 高级篇 -- 相对引用2（十三）

&#x1f48c; 所属专栏&#xff1a;【Git】 &#x1f600; 作  者&#xff1a;我是夜阑的狗&#x1f436; &#x1f680; 个人简介&#xff1a;一个正在努力学技术的CV工程师&#xff0c;专注基础和实战分享 &#xff0c;欢迎咨询&#xff01; &#x1f496; 欢迎大…
阅读更多...
面向对象9

面向对象9

面向对象9 一.内部类 1、什么是内部类&#xff1f; 将一个类A定义在另一个类B里面&#xff0c;里面的那个类A就称为内部类&#xff08;InnerClass&#xff09;&#xff0c;类B则称为外部类&#xff08;OuterClass&#xff09;。 2、为什么需要内部类&#xff1f; 具体来说…
阅读更多...
操作系统八股｜用户态和内核态

操作系统八股｜用户态和内核态

文章目录 内核态(Kernel Mode)用户态(User Mode)用户态和内核态之间的切换为什么要切换如何切换系统调用硬件中断异常处理 为了使操作系统内核提供⼀个⽆懈可击的进程抽象&#xff0c;处理器必须提供⼀种机制&#xff0c; 限制⼀个应⽤可以执⾏的指令以及他可以⽤来访问的地址…
阅读更多...
4.4C++

4.4C++

1 #include <iostream> #include <cmath> using namespace std; class A{ private:int a;// 判断一个数是否为质数bool isP(int num) {if (num<2) return false;for (int i2;i<sqrt(num);i) {if (num % i 0) {return false;}}return true;} public:// 构造…
阅读更多...
open-cd框架调试记录

open-cd框架调试记录

源于论文Changer: Feature Interaction Is What You Need forChange Detection 源码位置&#xff1a;open-cd/README.md at main likyoo/open-cd (github.com) 同样是基于MMSegmentation框架的代码&#xff0c;不符合本人编程习惯所以一直也没有研究这东西&#xff0c;近期打…
阅读更多...
Linux进程概念（二）：进程的基本概念与进程的创建

Linux进程概念（二）：进程的基本概念与进程的创建

目录 进程的基本概念 进程控制块-PCB 学前补充 预备知识 创建&#xff08;子&#xff09;进程 创建&#xff08;子&#xff09;进程的原因 理解fork有两个返回值 进程的基本概念 基本概念&#xff1a;程序的一个执行实例&#xff0c;正在执行的程序等 内核层面&#x…
阅读更多...
R语言数据分析基础（四）- 引用其他文件中的函数

R语言数据分析基础（四）- 引用其他文件中的函数

在R语言中&#xff0c;要引用其他文件中的函数&#xff0c;可以使用source()或load()函数。source()函数用于执行一个R脚本文件&#xff0c;而load()函数用于加载一个包含函数定义的R包。 使用source()函数引用其他文件中的函数&#xff1a; # 假设有一个名为my_functions.R的…
阅读更多...
（源码+讲解+部署）基于Spring Boot和Vue的考研教育系统的设计与实现

（源码+讲解+部署）基于Spring Boot和Vue的考研教育系统的设计与实现

前言 &#x1f497;博主介绍&#xff1a;✌专注于Java、小程序技术领域和毕业项目实战✌&#x1f497; &#x1f447;&#x1f3fb; 精彩专栏 推荐订阅&#x1f447;&#x1f3fb; 2024年Java精品实战案例《128套》 &#x1f345;文末获取源码联系&#x1f345; &#x1f31f…
阅读更多...
最新文章

Copyright @ 2022~2023