Redis集群搭建(主從模式、哨兵模式、集群模式)
更新時間：2024年01月09日 12:02:35 作者：242030
本文主要介紹了Redis集群搭建,主要包括主從模式、哨兵模式、集群模式這三種方式,文中通過示例代碼介紹的非常詳細,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧
1、主從模式部署
1.1 環(huán)境準備
| IP | 主機名 | 角色 |
|---|---|---|
| 192.168.54.200 | master | master |
| 192.168.54.201 | slave1 | slave1 |
| 192.168.54.202 | slave2 | slave2 |
1.2 下載
下載地址：http://download.redis.io/releases/
這里選擇下載：redis-7.0.3.tar.gz
1.3 上傳到服務器并且解壓(所有節(jié)點)
# 解壓 tar -xf redis-7.0.3.tar.gz cd redis-7.0.3 # 設置環(huán)境變量 echo "export REDIS_HOME=/home/zhangshixing/redis/redis-7.0.3">> /etc/profile source /etc/profile
1.4 編譯安裝(所有節(jié)點)
cd $REDIS_HOME yum -y install gcc gcc++ make && make install # 默認安裝目錄 /usr/local/bin
1.5 配置成服務(所有節(jié)點)
cat << EOF > /usr/lib/systemd/system/redis.service [Unit] Description=Redis persistent key-value database After=network.target After=network-online.target Wants=network-online.target [Service] ExecStart=/usr/local/bin/redis-server /usr/local/redis/redis.conf --supervised systemd ExecStop=/usr/libexec/redis-shutdown Type=forking User=redis Group=redis RuntimeDirectory=redis RuntimeDirectoryMode=0755 LimitNOFILE=65536 PrivateTmp=true [Install] WantedBy=multi-user.target EOF
配置描述：
Description: # 描述服務 After: # 描述服務類別 [Service]: # 服務運行參數(shù)的設置 Type=forking: # 是后臺運行的形式 ExecStart: # 為服務的具體運行命令 ExecReload: # 為重啟命令 ExecStop: # 為停止命令 LimitNOFILE=65536: # 打開文件數(shù)和進程數(shù)有限制,默認限制為1024,如果不設置,或者設置為LimitNOFILE=unlimited(不識別),則得到了1024 PrivateTmp=True: # 表示給服務分配獨立的臨時空間 #【注意】[Service]的啟動、重啟、停止命令全部要求使用絕對路徑 [Install]: # 運行級別下服務安裝的相關設置,可設置為多用戶,即系統(tǒng)運行級別為3
# 重載系統(tǒng)服務 systemctl daemon-reload
/usr/libexec/redis-shutdown的內(nèi)容：
#!/bin/bash
#
# Wrapper to close properly redis and sentinel
test x"$REDIS_DEBUG" != x && set -x
REDIS_CLI=/usr/local/bin/redis-cli
# Retrieve service name
SERVICE_NAME="$1"
if [ -z "$SERVICE_NAME" ]; then
SERVICE_NAME=redis
fi
# Get the proper config file based on service name
CONFIG_FILE="/usr/local/redis/$SERVICE_NAME.conf"
# Use awk to retrieve host, port from config file
HOST=`awk '/^[[:blank:]]*bind/ { print $2 }' $CONFIG_FILE | tail -n1`
PORT=`awk '/^[[:blank:]]*port/ { print $2 }' $CONFIG_FILE | tail -n1`
PASS=`awk '/^[[:blank:]]*requirepass/ { print $2 }' $CONFIG_FILE | tail -n1`
SOCK=`awk '/^[[:blank:]]*unixsocket\s/ { print $2 }' $CONFIG_FILE | tail -n1`
# Just in case, use default host, port
HOST=${HOST:-127.0.0.1}
if [ "$SERVICE_NAME" = redis ]; then
PORT=${PORT:-6379}
else
PORT=${PORT:-26739}
fi
# Setup additional parameters
# e.g password-protected redis instances
[ -z "$PASS" ] || ADDITIONAL_PARAMS="-a $PASS"
# shutdown the service properly
if [ -e "$SOCK" ] ; then
$REDIS_CLI -s $SOCK $ADDITIONAL_PARAMS shutdown
else
$REDIS_CLI -h $HOST -p $PORT $ADDITIONAL_PARAMS shutdown
fi
配置完就可以通過systemctl啟停redis了。
1.6 授權(quán)啟動服務(所有節(jié)點)
chmod +x /usr/libexec/redis-shutdown useradd -s /sbin/nologin redis mkdir /usr/local/redis ; cp $REDIS_HOME/redis.conf /usr/local/redis/ && chown -R redis:redis /usr/local/redis mkdir -p /opt/software/redis-7.0.3/data && chown -R redis:redis /opt/software/redis-7.0.3/data # 命令補全 yum install -y bash-completion && source /etc/profile systemctl daemon-reload systemctl enable redis
1.7 修改linux內(nèi)核參數(shù)(所有節(jié)點)
# 臨時生效 sysctl -w vm.overcommit_memory=1 # 永久生效 echo 'vm.overcommit_memory=1' >> /etc/sysctl.conf && sysctl -p # 可選值：0,1,2。 # 0: 表示內(nèi)核將檢查是否有足夠的可用內(nèi)存供應用進程使用;如果有足夠的可用內(nèi)存,內(nèi)存申請允許;否則,內(nèi)存申請失敗,并把錯誤返回給應用進程。 # 1: 表示內(nèi)核允許分配所有的物理內(nèi)存,而不管當前的內(nèi)存狀態(tài)如何。 # 2: 表示內(nèi)核允許分配超過所有物理內(nèi)存和交換空間總和的內(nèi)存。
1.8 配置(redis.conf)
1.8.1 master節(jié)點配置
修改配置如下：
vi /usr/local/redis/redis.conf
bind 192.168.54.200 # 監(jiān)聽ip,多個ip用空格分隔 daemonize yes # 允許后臺啟動 logfile "/usr/local/redis/redis.log" # 日志路徑 dir /opt/software/redis-7.0.3/data # 數(shù)據(jù)庫備份文件存放目錄 masterauth 123456 # slave連接master密碼,master可省略 requirepass 123456 # 設置master連接密碼,slave可省略 appendonly yes # 在/opt/software/redis-7.0.3/data目錄生成appendonly.aof文件，將每一次寫操作請求都追加到appendonly.aof 文件中
1.8.2 slave1節(jié)點配置
修改配置如下：
vi /usr/local/redis/redis.conf
bind 192.168.182.201 # 監(jiān)聽ip,多個ip用空格分隔 daemonize yes # 允許后臺啟動 logfile "/usr/local/redis/redis.log" # 日志路徑 dir /opt/software/redis-7.0.3/data # 數(shù)據(jù)庫備份文件存放目錄 # replicaof用于追隨某個節(jié)點的redis,被追隨的節(jié)點為主節(jié)點,追隨的為從節(jié)點,就是設置master節(jié)點 replicaof 192.168.182.200 6379 masterauth 123456 # slave連接master密碼，master可省略 requirepass 123456 # 設置master連接密碼，slave可省略 appendonly yes # 在/opt/software/redis-7.0.3/data目錄生成appendonly.aof文件，將每一次寫操作請求都追加到appendonly.aof 文件中
1.8.3 slave2節(jié)點配置
修改配置如下：
vi /usr/local/redis/redis.conf
bind 192.168.182.202 # 監(jiān)聽ip，多個ip用空格分隔 daemonize yes # 允許后臺啟動 logfile "/usr/local/redis/redis.log" # 日志路徑 dir /opt/software/redis-7.0.3/data # 數(shù)據(jù)庫備份文件存放目錄 # replicaof用于追隨某個節(jié)點的redis,被追隨的節(jié)點為主節(jié)點,追隨的為從節(jié)點,就是設置master節(jié)點 replicaof 192.168.182.200 6379 masterauth 123456 # slave連接master密碼，master可省略 requirepass 123456 # 設置master連接密碼，slave可省略 appendonly yes # 在/opt/software/redis-7.0.3/data目錄生成appendonly.aof文件，將每一次寫操作請求都追加到appendonly.aof 文件中
1.9 啟動Redis服務(所有節(jié)點)
systemctl start redis systemctl status redis
1.10 查看集群狀態(tài)
# 交互式 [root@master redis]# redis-cli -h 192.168.54.200 -a 123456 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. 192.168.54.200:6379> info replication # Replication role:master connected_slaves:2 slave0:ip=192.168.54.201,port=6379,state=online,offset=1204,lag=0 slave1:ip=192.168.54.202,port=6379,state=online,offset=1204,lag=1 master_failover_state:no-failover master_replid:e85f46b61089c38974769a2faa2fb905d4efc66f master_replid2:0000000000000000000000000000000000000000 master_repl_offset:1204 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:1204
# 非交互式 [root@master redis]# redis-cli -h 192.168.54.200 -a 123456 info replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. # Replication role:master connected_slaves:2 slave0:ip=192.168.54.201,port=6379,state=online,offset=1288,lag=1 slave1:ip=192.168.54.202,port=6379,state=online,offset=1288,lag=1 master_failover_state:no-failover master_replid:e85f46b61089c38974769a2faa2fb905d4efc66f master_replid2:0000000000000000000000000000000000000000 master_repl_offset:1288 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:1288
# 交互式 [root@master redis]# redis-cli -h 192.168.54.200 -a 123456 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. 192.168.54.200:6379> auth 123456 OK 192.168.54.200:6379> info replication # Replication role:master connected_slaves:2 slave0:ip=192.168.54.201,port=6379,state=online,offset=1372,lag=1 slave1:ip=192.168.54.202,port=6379,state=online,offset=1372,lag=1 master_failover_state:no-failover master_replid:e85f46b61089c38974769a2faa2fb905d4efc66f master_replid2:0000000000000000000000000000000000000000 master_repl_offset:1372 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:1372
在這里Redis的主從模式就部署完了（一主兩從）。
2、Sentinel(哨兵)模式部署
2.1 環(huán)境準備
| IP | 主機名 | 角色 |
|---|---|---|
| 192.168.54.200 | master | master,Sentinel |
| 192.168.54.201 | slave1 | slave1,Sentinel |
| 192.168.54.202 | slave2 | slave2,Sentinel |
【溫馨提示】 sentinel 最好跟redis部署在不同的機器上，sentinel 端口：26379。
2.2 配置sentinel(所有節(jié)點)
【溫馨提示】前面已經(jīng)安裝過了redis主從模式了，因為哨兵模式是基于主從模式的，所以redis的配置這里就省略
了，直接修改sentinel配置文件，配置3個哨兵，每個哨兵的配置都是一樣的。
# 三個節(jié)點創(chuàng)建存儲目錄 mkdir /opt/software/redis-7.0.3/sentinel; chown -R redis:redis /opt/software/redis-7.0.3/sentinel cat >/usr/local/redis/sentinel.conf<<EOF daemonize yes logfile "/usr/local/redis/sentinel.log" # sentinel工作目錄 dir "/opt/software/redis-7.0.3/sentinel" # 判斷master失效至少需要2個sentinel同意，建議設置為n/2+1,n為sentinel個數(shù) # sentinel monitor <master-name> <ip> <port> <count> sentinel monitor mymaster 192.168.54.200 6379 2 sentinel auth-pass mymaster 123456 # 判斷master主觀下線時間，默認30s sentinel down-after-milliseconds mymaster 30000 EOF
2.3 啟動sentinel(所有節(jié)點)
nohup /usr/local/bin/redis-sentinel /usr/local/redis/sentinel.conf >> nohup.out 2>&1 & netstat -tnlp|grep 26379
2.4 模擬故障測試
# 停掉master systemctl stop redis redis-cli -h 192.168.54.201 -a 123456 info replication
[root@master redis]# redis-cli -h 192.168.54.201 -a 123456 info replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. # Replication role:slave master_host:192.168.54.200 master_port:6379 master_link_status:down master_last_io_seconds_ago:-1 master_sync_in_progress:0 slave_read_repl_offset:20712 slave_repl_offset:20712 master_link_down_since_seconds:18 slave_priority:100 slave_read_only:1 replica_announced:1 connected_slaves:0 master_failover_state:no-failover master_replid:e85f46b61089c38974769a2faa2fb905d4efc66f master_replid2:0000000000000000000000000000000000000000 master_repl_offset:20712 second_repl_offset:-1 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:20712
[root@master redis]# redis-cli -h 192.168.54.201 -a 123456 info replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. # Replication role:slave master_host:192.168.54.202 master_port:6379 master_link_status:up master_last_io_seconds_ago:1 master_sync_in_progress:0 slave_read_repl_offset:29371 slave_repl_offset:29371 slave_priority:100 slave_read_only:1 replica_announced:1 connected_slaves:0 master_failover_state:no-failover master_replid:7a7fe0a8528e0c7913d5d54bc5ba633ab6879a8c master_replid2:e85f46b61089c38974769a2faa2fb905d4efc66f master_repl_offset:29371 second_repl_offset:20713 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:1 repl_backlog_histlen:29371
發(fā)現(xiàn)master節(jié)點已經(jīng)切換到其它節(jié)點了，再測試一下讀寫：
[root@master redis]# redis-cli -h 192.168.54.202 -a 123456 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. 192.168.54.202:6379> set k2 v2 OK
新的master節(jié)點寫能力也正常，接下來就是恢復故障了。
# 啟動master systemctl start redis redis-cli -h 192.168.54.202 -a 123456 info replication
[root@master redis]# redis-cli -h 192.168.54.202 -a 123456 info replication Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. # Replication role:master connected_slaves:2 slave0:ip=192.168.54.201,port=6379,state=online,offset=70444,lag=0 slave1:ip=192.168.54.200,port=6379,state=online,offset=70444,lag=0 master_failover_state:no-failover master_replid:7a7fe0a8528e0c7913d5d54bc5ba633ab6879a8c master_replid2:e85f46b61089c38974769a2faa2fb905d4efc66f master_repl_offset:70587 second_repl_offset:20713 repl_backlog_active:1 repl_backlog_size:1048576 repl_backlog_first_byte_offset:869 repl_backlog_histlen:69719
發(fā)現(xiàn)就算原先的master節(jié)點恢復了，也不會切換到master角色，而是作為slave角色。
3、Cluster模式部署
使用集群，只需要將redis配置文件中的cluster-enable配置打開即可。
3.1 環(huán)境準備
| IP | 端口 | 節(jié)點 |
|---|---|---|
| 192.168.54.200 | 7001,7002,7003 | node1 |
| 192.168.54.201 | 7001,7002,7003 | node2 |
| 192.168.54.202 | 7001,7002,7003 | node3 |
3.2 修改配置(所有節(jié)點)
【溫馨提示】這里是基于主從模式的配置修改，不是基于主從模式部署，哨兵模式是基于主從模式部署。
# 創(chuàng)建存儲目錄
mkdir -p /opt/software/redis-7.0.3/cluster/redis_{7001..7003}
cp /usr/local/redis/redis.conf /usr/local/redis/cluster_redis_7001.conf
cp /usr/local/redis/redis.conf /usr/local/redis/cluster_redis_7002.conf
cp /usr/local/redis/redis.conf /usr/local/redis/cluster_redis_7003.conf
chown -R redis:redis /usr/local/redis ;chown -R redis:redis /opt/software/redis-7.0.3/cluster
修改配置文件/usr/local/redis/cluster_redis_7001.conf
# 【注意】節(jié)點不一樣，IP不一樣，記得修改這個bind配置 bind 192.168.54.200 port 7001 daemonize yes pidfile "/var/run/cluster_redis_7001.pid" logfile "/usr/local/redis/cluster_redis_7001.log" dir "/opt/software/redis-7.0.3/cluster/redis_7001" masterauth "123456" requirepass "123456" # replicaof 192.168.54.202 6379 appendonly yes # 開啟集群模式 cluster-enabled yes # 雖然此配置的名字叫"集群配置文件"，但是此配置文件不能人工編輯，它是集群節(jié)點自動維護的文件，主要用于記錄集群中有哪些節(jié)點、他們的狀態(tài)以及一些持久化參數(shù)等，方便在重啟時恢復這些狀態(tài)。通常是在收到請求之后這個文件就會被更新。 cluster-config-file nodes_7001.conf cluster-node-timeout 15000
修改配置文件/usr/local/redis/cluster_redis_7002.conf
# 【注意】節(jié)點不一樣，IP不一樣，記得修改這個bind配置 bind 192.168.54.200 port 7002 daemonize yes pidfile "/var/run/cluster_redis_7002.pid" logfile "/usr/local/redis/cluster_redis_7002.log" dir "/opt/software/redis-7.0.3/cluster/redis_7002" masterauth "123456" requirepass "123456" # replicaof 192.168.54.202 6379 appendonly yes # 配置yes則開啟集群功能，此redis實例作為集群的一個節(jié)點，否則，它是一個普通的單一的redis實例。 cluster-enabled yes # 雖然此配置的名字叫"集群配置文件"，但是此配置文件不能人工編輯，它是集群節(jié)點自動維護的文件，主要用于記錄集群中有哪些節(jié)點、他們的狀態(tài)以及一些持久化參數(shù)等，方便在重啟時恢復這些狀態(tài)。通常是在收到請求之后這個文件就會被更新。 cluster-config-file nodes_7002.conf cluster-node-timeout 15000
修改配置文件/usr/local/redis/cluster_redis_7002.conf
# 【注意】節(jié)點不一樣，IP不一樣，記得修改這個bind配置 bind 192.168.54.200 port 7003 daemonize yes pidfile "/var/run/cluster_redis_7003.pid" logfile "/usr/local/redis/cluster_redis_7003.log" dir "/opt/software/redis-7.0.3/cluster/redis_7003" masterauth "123456" requirepass "123456" # replicaof 192.168.54.202 6379 appendonly yes # 配置yes則開啟集群功能，此redis實例作為集群的一個節(jié)點，否則，它是一個普通的單一的redis實例。 cluster-enabled yes # 雖然此配置的名字叫"集群配置文件"，但是此配置文件不能人工編輯，它是集群節(jié)點自動維護的文件，主要用于記錄集群中有哪些節(jié)點、他們的狀態(tài)以及一些持久化參數(shù)等，方便在重啟時恢復這些狀態(tài)。通常是在收到請求之后這個文件就會被更新。 cluster-config-file nodes_7003.conf cluster-node-timeout 15000
其它兩臺機器配置與192.168.54.2000一致，只是ip不同，此處省略。
# 將配置copy到另外兩個節(jié)點
scp -r /usr/local/redis/cluster_redis_{7001..7003}.conf 192.168.54.201:/usr/local/redis/
scp -r /usr/local/redis/cluster_redis_{7001..7003}.conf 192.168.54.202:/usr/local/redis/
# 在node2上執(zhí)行
sed -i 's/192.168.54.200/192.168.54.201/g' /usr/local/redis/cluster_redis_{7001..7003}.conf
# 在node3上執(zhí)行
sed -i 's/192.168.54.200/192.168.54.202/g' /usr/local/redis/cluster_redis_{7001..7003}.conf
3.3 啟動Redis服務(所有節(jié)點)
nohup redis-server /usr/local/redis/cluster_redis_7001.conf >> nohup.out 2>&1 & netstat -tnlp|grep 7001 nohup redis-server /usr/local/redis/cluster_redis_7002.conf >> nohup.out 2>&1 & netstat -tnlp|grep 7002 nohup redis-server /usr/local/redis/cluster_redis_7003.conf >> nohup.out 2>&1 & netstat -tnlp|grep 7003 tail -f /usr/local/redis/cluster_redis_7001.log tail -f /usr/local/redis/cluster_redis_7002.log tail -f /usr/local/redis/cluster_redis_7003.log
3.4 創(chuàng)建集群
# --cluster-replicas 2 : 表示集群的一個主節(jié)點有2個從節(jié)點，就是一主兩從模式 # 如果不加--cluster-replicas 2則會創(chuàng)建9個主節(jié)點 # --cluster / -c 告知redis-cli命令行工具，后續(xù)操作為cluster模式下 # --create 表示創(chuàng)建cluster模式 redis-cli -a 123456 --cluster create \ 192.168.54.200:7001 192.168.54.200:7002 192.168.54.200:7003 \ 192.168.54.201:7001 192.168.54.201:7002 192.168.54.201:7003 \ 192.168.54.202:7001 192.168.54.202:7002 192.168.54.202:7003 \ --cluster-replicas 2
[root@master redis]# redis-cli -a 123456 --cluster create \ > 192.168.54.200:7001 192.168.54.200:7002 192.168.54.200:7003 \ > 192.168.54.201:7001 192.168.54.201:7002 192.168.54.201:7003 \ > 192.168.54.202:7001 192.168.54.202:7002 192.168.54.202:7003 \ > --cluster-replicas 2 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. >>> Performing hash slots allocation on 9 nodes... Master[0] -> Slots 0 - 5460 Master[1] -> Slots 5461 - 10922 Master[2] -> Slots 10923 - 16383 Adding replica 192.168.54.201:7002 to 192.168.54.200:7001 Adding replica 192.168.54.202:7002 to 192.168.54.200:7001 Adding replica 192.168.54.200:7003 to 192.168.54.201:7001 Adding replica 192.168.54.202:7003 to 192.168.54.201:7001 Adding replica 192.168.54.201:7003 to 192.168.54.202:7001 Adding replica 192.168.54.200:7002 to 192.168.54.202:7001 M: d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001 slots:[0-5460] (5461 slots) master S: 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002 replicates 41d651cdefd81e8b2249cf9a99d151920a2e793e S: 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003 replicates 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 M: 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001 slots:[5461-10922] (5462 slots) master S: 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002 replicates d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 S: 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003 replicates 41d651cdefd81e8b2249cf9a99d151920a2e793e M: 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001 slots:[10923-16383] (5461 slots) master S: ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002 replicates d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 S: bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003 replicates 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 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.54.200:7001) M: d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001 slots:[0-5460] (5461 slots) master 2 additional replica(s) S: 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002 slots: (0 slots) slave replicates d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 S: 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003 slots: (0 slots) slave replicates 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 S: bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003 slots: (0 slots) slave replicates 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 M: 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001 slots:[5461-10922] (5462 slots) master 2 additional replica(s) M: 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001 slots:[10923-16383] (5461 slots) master 2 additional replica(s) S: 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003 slots: (0 slots) slave replicates 41d651cdefd81e8b2249cf9a99d151920a2e793e S: 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002 slots: (0 slots) slave replicates 41d651cdefd81e8b2249cf9a99d151920a2e793e S: ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002 slots: (0 slots) slave replicates d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 [OK] All nodes agree about slots configuration. >>> Check for open slots... >>> Check slots coverage... [OK] All 16384 slots covered.
會自動生成nodes.conf文件
[root@master redis]# ll /opt/software/redis-7.0.3/cluster/redis_{7001..7003}
/opt/software/redis-7.0.3/cluster/redis_7001:
總用量 4
drwxr-xr-x. 2 root root 103 12月 20 16:48 appendonlydir
-rw-r--r--. 1 root root 1237 12月 20 16:49 nodes_7001.conf
/opt/software/redis-7.0.3/cluster/redis_7002:
總用量 8
drwxr-xr-x. 2 root root 103 12月 20 16:49 appendonlydir
-rw-r--r--. 1 root root 171 12月 20 16:49 dump.rdb
-rw-r--r--. 1 root root 1237 12月 20 16:49 nodes_7002.conf
/opt/software/redis-7.0.3/cluster/redis_7003:
總用量 8
drwxr-xr-x. 2 root root 103 12月 20 16:49 appendonlydir
-rw-r--r--. 1 root root 171 12月 20 16:49 dump.rdb
-rw-r--r--. 1 root root 1237 12月 20 16:49 nodes.conf
3.5 集群操作
3.5.1 登錄集群
redis-cli -c -h 192.168.54.200 -p 7001
3.5.2 查看集群信息
> auth 123456 > CLUSTER INFO
3.5.3 列出節(jié)點信息
> CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.200 -p 7001 192.168.54.200:7001> auth 123456 OK 192.168.54.200:7001> CLUSTER INFO cluster_state:ok cluster_slots_assigned:16384 cluster_slots_ok:16384 cluster_slots_pfail:0 cluster_slots_fail:0 cluster_known_nodes:9 cluster_size:3 cluster_current_epoch:9 cluster_my_epoch:1 cluster_stats_messages_ping_sent:233 cluster_stats_messages_pong_sent:247 cluster_stats_messages_sent:480 cluster_stats_messages_ping_received:239 cluster_stats_messages_pong_received:233 cluster_stats_messages_meet_received:8 cluster_stats_messages_received:480 total_cluster_links_buffer_limit_exceeded:0 192.168.54.200:7001> CLUSTER NODES 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671526417098 1 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 myself,master - 0 1671526415000 1 connected 0-5460 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671526419115 4 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671526418107 4 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671526417000 4 connected 5461-10922 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671526418000 7 connected 10923-16383 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671526419000 7 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671526418000 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671526416000 1 connected 192.168.54.200:7001>
3.5.4 增加節(jié)點
node1上增加一節(jié)點
【1】配置
# copy配置 cp /usr/local/redis/cluster_redis_7003.conf /usr/local/redis/cluster_redis_7004.conf # 創(chuàng)建存儲目錄 mkdir /opt/software/redis-7.0.3/cluster/redis_7004 # 修改配置 vi /usr/local/redis/cluster_redis_7004.conf bind 192.168.54.200 port 7004 daemonize yes pidfile "/var/run/redis_7004.pid" logfile "/usr/local/redis/cluster_redis_7004.log" dir "/opt/software/redis-7.0.3/cluster/redis_7004" #replicaof 192.168.182.110 6379 masterauth "123456" requirepass "123456" appendonly yes cluster-enabled yes cluster-config-file nodes_7004.conf cluster-node-timeout 15000 # 授權(quán) chown -R redis:redis /usr/local/redis && chown -R redis:redis /opt/software/redis-7.0.3/cluster/redis_7004
【2】啟動服務
nohup redis-server /usr/local/redis/cluster_redis_7004.conf >> nohup.out 2>&1 & netstat -tnlp|grep 7004
【3】集群中增加節(jié)點
[root@local-168-182-110 ~]# redis-cli -c -h 192.168.54.200 -p 7001 > auth 123456 # 添加節(jié)點 > CLUSTER MEET 192.168.54.200 7004 # 查看節(jié)點信息 > CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.200 -p 7001 192.168.54.200:7001> auth 123456 OK 192.168.54.200:7001> CLUSTER MEET 192.168.54.200 7004 OK 192.168.54.200:7001> CLUSTER NODES a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 master - 0 1671527132044 0 connected 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527134063 1 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 myself,master - 0 1671527131000 1 connected 0-5460 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527132000 4 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527132000 4 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527133000 4 connected 5461-10922 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527133567 7 connected 10923-16383 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527132000 7 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527133051 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527131000 1 connected
可以看到，新增的節(jié)點都是以master身份加入集群的
【4】更換節(jié)點身份
將新增的192.168.54.200:7004節(jié)點身份改為192.168.54.200:7001的slave：
redis-cli -c -h 192.168.54.200 -p 7004 > auth 123456 # 改變節(jié)點類型 > cluster replicate d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 > CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.200 -p 7004 192.168.54.200:7004> auth 123456 OK 192.168.54.200:7004> CLUSTER NODES 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527454000 1 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527451000 7 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527452371 4 connected 5461-10922 d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 master - 0 1671527455399 1 connected 0-5460 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527454000 7 connected 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527453000 7 connected 10923-16383 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527453883 4 connected a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 myself,master - 0 1671527448000 0 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527451000 4 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527455000 1 connected 192.168.54.200:7004> cluster replicate d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 OK 192.168.54.200:7004> CLUSTER NODES 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527488000 1 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527490723 7 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527489000 4 connected 5461-10922 d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 master - 0 1671527489713 1 connected 0-5460 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527486675 7 connected 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527489598 7 connected 10923-16383 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527487000 4 connected a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 myself,slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527486000 1 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527487683 4 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527488691 1 connected
3.5.5 刪除節(jié)點
redis-cli -c -h 192.168.54.200 -p 7001 > auth 123456 # 查看節(jié)點 > CLUSTER NODES # 刪除節(jié)點 > CLUSTER FORGET a9b489648b4acc38bfc04499767f808b7208cb1f # 檢查節(jié)點信息 > CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.200 -p 7001 192.168.54.200:7001> auth 123456 OK 192.168.54.200:7001> CLUSTER NODES a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527601411 1 connected 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527598000 1 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 myself,master - 0 1671527595000 1 connected 0-5460 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527600403 4 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527599000 4 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527599393 4 connected 5461-10922 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527598000 7 connected 10923-16383 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527597374 7 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527597000 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527600000 1 connected 192.168.54.200:7001> CLUSTER FORGET a9b489648b4acc38bfc04499767f808b7208cb1f OK 192.168.54.200:7001> 192.168.54.200:7001> CLUSTER NODES 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527636743 1 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 myself,master - 0 1671527636000 1 connected 0-5460 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527635733 4 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527637753 4 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527635000 4 connected 5461-10922 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527632000 7 connected 10923-16383 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527634724 7 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527635000 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527632206 1 connected
3.5.6 保存配置
redis-cli -c -h 192.168.54.200 -p 7001 > auth 123456 # 將節(jié)點的配置文件保存到硬盤里面 > CLUSTER SAVECONFIG > CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.200 -p 7001 192.168.54.200:7001> auth 123456 OK 192.168.54.200:7001> CLUSTER SAVECONFIG OK 192.168.54.200:7001> CLUSTER NODES a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527763975 1 connected 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527763000 1 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 myself,master - 0 1671527762000 1 connected 0-5460 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527760000 4 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671527759929 4 connected 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 master - 0 1671527759000 4 connected 5461-10922 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671527761000 7 connected 10923-16383 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527762964 7 connected 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671527762000 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 0 1671527761956 1 connected
可以看到，之前刪除的節(jié)點又恢復了，這是因為對應的配置文件沒有刪除，執(zhí)行CLUSTER SAVECONFIG恢復。
3.5.7 模擬master節(jié)點掛掉
netstat -lntp |grep :7001|awk '{print $NF}'|cut -d '/' -f 1|xargs kill -9
redis-cli -c -h 192.168.54.201 -p 7001 -a 123456 CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.201 -p 7001 -a 123456 CLUSTER NODES Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671528090000 7 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671528090000 4 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 master,fail - 1671528024512 1671528017000 1 disconnected 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671528094858 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave a9b489648b4acc38bfc04499767f808b7208cb1f 0 1671528093000 10 connected 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave a9b489648b4acc38bfc04499767f808b7208cb1f 0 1671528093843 10 connected 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671528091000 7 connected 10923-16383 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 myself,master - 0 1671528093000 4 connected 5461-10922 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671528092000 4 connected a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 master - 0 1671528092000 10 connected 0-5460
對應192.168.54.200:7001的一行可以看到，master fail，狀態(tài)為disconnected；而對應
192.168.54.200:7004的一行，slave已經(jīng)變成master。
【故障恢復】重新啟動192.168.54.200:7001節(jié)點
nohup redis-server /usr/local/redis/cluster_redis_7001.conf >> nohup.out 2>&1 & redis-cli -c -h 192.168.54.201 -p 7001 -a 123456 CLUSTER NODES
[root@master redis]# redis-cli -c -h 192.168.54.201 -p 7001 -a 123456 CLUSTER NODES Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. 6999efc73a2d128d8583139074929fa144f43d78 192.168.54.200:7002@17002 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671528205550 7 connected bdadcef4ac56abebb545c0cb69c509f8a7491bef 192.168.54.202:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671528206457 4 connected d88cfb0ee3c53547ce7f1f237655fbd3cd6a7a42 192.168.54.200:7001@17001 slave a9b489648b4acc38bfc04499767f808b7208cb1f 0 1671528206000 10 connected 9e95afd03e0b3e019ff81e5dcf78f962830bca69 192.168.54.201:7003@17003 slave 41d651cdefd81e8b2249cf9a99d151920a2e793e 0 1671528206000 7 connected ee7300d10e1fd6f52b221b639367e9a6d55d85d5 192.168.54.202:7002@17002 slave a9b489648b4acc38bfc04499767f808b7208cb1f 0 1671528208475 10 connected 18c654e7a1df333c456aa119a2cf36a0c8272165 192.168.54.201:7002@17002 slave a9b489648b4acc38bfc04499767f808b7208cb1f 0 1671528206000 10 connected 41d651cdefd81e8b2249cf9a99d151920a2e793e 192.168.54.202:7001@17001 master - 0 1671528206558 7 connected 10923-16383 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 192.168.54.201:7001@17001 myself,master - 0 1671528205000 4 connected 5461-10922 0adc0cb28eb662df3f139ee4a6752d187297a443 192.168.54.200:7003@17003 slave 358f827f29b05016fb1f57c88cbdeb7dbfc613f5 0 1671528207466 4 connected a9b489648b4acc38bfc04499767f808b7208cb1f 192.168.54.200:7004@17004 master - 0 1671528206000 10 connected 0-5460
可以看到，192.168.54.200:7001節(jié)點啟動后為slave節(jié)點，并且是192.168.54.200:7004的slave節(jié)點。即
master節(jié)點如果掛掉，它的slave節(jié)點變?yōu)樾耺aster節(jié)點繼續(xù)對外提供服務，而原來的master節(jié)點如果重啟，則
變?yōu)樾耺aster節(jié)點的slave節(jié)點。
【溫馨提示】cluster不能選擇db，只能默認db為0，所以select切庫相當于是不能使用的。
4、簡單使用
4.1 集群常用操作
4.1.1 查看集群信息
# 打印集群的信息 cluster info # 列出集群當前已知的所有節(jié)點(node),以及這些節(jié)點的相關信息 cluster nodes
4.1.2 節(jié)點操作
# 將ip和port所指定的節(jié)點添加到集群當中,讓它成為集群的一份子 cluster meet <ip> <port> # 從集群中移除node_id指定的節(jié)點 cluster forget <node_id> # 將當前節(jié)點設置為node_id指定的節(jié)點的從節(jié)點 cluster replicate <node_id> # 將節(jié)點的配置文件保存到硬盤里面 cluster saveconfig
4.1.3 槽(slot)
# 將一個或多個槽(slot)指派(assign)給當前節(jié)點 cluster addslots <slot> [slot ...] # 移除一個或多個槽對當前節(jié)點的指派 cluster delslots <slot> [slot ...] # 移除指派給當前節(jié)點的所有槽,讓當前節(jié)點變成一個沒有指派任何槽的節(jié)點 cluster flushslots # 將槽slot指派給node_id指定的節(jié)點,如果槽已經(jīng)指派給另一個節(jié)點 # 那么先讓另一個節(jié)點刪除該槽,然后再進行指派 cluster setslot <slot> node <node_id> # 將本節(jié)點的槽slot遷移到node_id指定的節(jié)點中 cluster setslot <slot> migrating <node_id> # 從node_id指定的節(jié)點中導入槽slot到本節(jié)點 cluster setslot <slot> importing <node_id> # 取消對槽slot的導入(import)或者遷移(migrate) cluster setslot <slot> stable
4.1.4 鍵
# 計算鍵key應該被放置在哪個槽上 cluster keyslot <key> # 返回槽slot目前包含的鍵值對數(shù)量 cluster countkeysinslot <slot> # 返回count個slot槽中的鍵 cluster getkeysinslot <slot> <count>
4.2 redis 常用操作
4.2.1 字符串(String)
# 登錄master節(jié)點，slave節(jié)點是只讀的 redis-cli -c -h 192.168.182.112 -p 7001 192.168.182.112:7001> auth 123456 OK 192.168.182.112:7001> set k1 v1 OK 192.168.182.112:7001> get k1 "v1" # 獲取多個值 192.168.182.112:7001> mget k1 k2 k3 1) "v1" 2) "v2" 3) "v3"
4.2.2 哈希(Hash)
Redis hash 是一個 string 類型的 field（字段） 和 value（值） 的映射表，hash 特別適合用于存儲對象。
# 登錄master節(jié)點，slave節(jié)點是只讀的 redis-cli -c -h 192.168.182.112 -p 7001 192.168.182.112:7001> auth 123456 # 設置 192.168.182.112:7001> HSET myhash field1 "foo" (integer) 1 # 獲取 192.168.182.112:7001> hget myhash field1 "foo"
4.2.3 列表(List)
Redis列表是簡單的字符串列表，按照插入順序排序。你可以添加一個元素到列表的頭部（左邊）或者尾部（右
邊）。
# 登錄master節(jié)點,slave節(jié)點是只讀的 redis-cli -c -h 192.168.182.112 -p 7001 192.168.182.112:7001> auth 123456 192.168.182.112:7001> LPUSH larr v1 (integer) 1 192.168.182.112:7001> LPUSH larr v2 (integer) 2 192.168.182.112:7001> LPUSH larr v3 (integer) 3 # 獲取0到10個元素 192.168.182.112:7001> LRANGE larr 0 10 1) "v3" 2) "v2" 3) "v1"
4.2.4 集合(Set)
Redis 的 Set 是 String 類型的無序集合。集合成員是唯一的，這就意味著集合中不能出現(xiàn)重復的數(shù)據(jù)。
# 登錄master節(jié)點,slave節(jié)點是只讀的 redis-cli -c -h 192.168.182.112 -p 7001 192.168.182.112:7001> auth 123456 192.168.182.112:7001> SADD myset "hello" (integer) 1 192.168.182.112:7001> SADD myset "foo" (integer) 1 # 已經(jīng)存在,則不能添加該元素 192.168.182.112:7001> SADD myset "hello" (integer) 0 # 獲取 192.168.182.112:7001> SMEMBERS myset 1) "foo" 2) "hello" 192.168.182.112:6379>
4.2.5 有序集合(sorted set)
Redis 有序集合和集合一樣也是 string 類型元素的集合，且不允許重復的成員。不同的是每個元素都會關聯(lián)一個
double 類型的分數(shù)。redis 正是通過分數(shù)來為集合中的成員進行從小到大的排序。有序集合的成員是唯一的，但
分數(shù)(score)卻可以重復。
# 登錄master節(jié)點,slave節(jié)點是只讀的 redis-cli -c -h 192.168.182.112 -p 7001 192.168.182.112:7001> auth 123456 192.168.182.112:7001> ZADD key1 1 redis (integer) 1 192.168.182.112:7001> ZADD key1 2 mongodb (integer) 1 192.168.182.112:7001> ZADD key1 3 mysql (integer) 1 # 已經(jīng)存在,不能添加 192.168.182.112:7001> ZADD key1 3 mysql (integer) 0 # 已經(jīng)存在,不能添加 192.168.182.112:7001> ZADD key1 4 mysql (integer) 0 # 獲取數(shù)據(jù) 192.168.182.112:7001> ZRANGE key1 0 10 WITHSCORES 1) "redis" 2) "1" 3) "mongodb" 4) "2" 5) "mysql" 6) "4"
到此這篇關于Redis集群搭建(主從模式、哨兵模式、集群模式)的文章就介紹到這了,更多相關Redis集群搭建內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關文章希望大家以后多多支持腳本之家！
相關文章
本文主要介紹了Redis高可用部署架構(gòu)的實現(xiàn),文中通過示例代碼介紹的非常詳細,對大家的學習或者工作具有一定的參考學習價值,需要的朋友們下面隨著小編來一起學習學習吧2023-08-08
這篇文章主要介紹了redis-cli?命令詳解,主要包括命令使用及使用info命令獲取服務器的信息，本文給大家介紹的非常詳細，對大家的學習或工作具有一定的參考借鑒價值，需要的朋友可以參考下2022-10-10
本文主要介紹了Redis Stream類型的使用詳解，文中通過示例代碼介紹的非常詳細，具有一定的參考價值，感興趣的小伙伴們可以參考一下2021-11-11
Linux系統(tǒng)下安裝Redis數(shù)據(jù)庫過程
大家好，本篇文章主要講的是Linux系統(tǒng)下安裝Redis數(shù)據(jù)庫過程，感興趣的同學趕快來看一看吧，對你有幫助的話記得收藏一下，方便下次瀏覽2021-12-12
從MySQL到Redis的簡單數(shù)據(jù)庫遷移方法
這篇文章主要介紹了從MySQL到Redis的簡單數(shù)據(jù)庫遷移方法,注意Redis數(shù)據(jù)庫基于內(nèi)存,并不能代替?zhèn)鹘y(tǒng)數(shù)據(jù)庫,需要的朋友可以參考下2015-06-06
本文主要介紹了Redis腦裂導致數(shù)據(jù)丟失的解決，文中通過示例代碼介紹的非常詳細，對大家的學習或者工作具有一定的參考學習價值，需要的朋友們下面隨著小編來一起學習學習吧2023-01-01
本文主要介紹了Redis中Hash類型的使用，文中通過示例代碼介紹的非常詳細，對大家的學習或者工作具有一定的參考學習價值，需要的朋友們下面隨著小編來一起學習學習吧2023-06-06
這篇文章主要介紹了redis實現(xiàn)簡單分布式鎖,文中通過代碼示例講解的非常詳細,需要的朋友可以參考下2013-09-09
本文主要介紹了Redis實現(xiàn)短信登錄的示例代碼，文中通過示例代碼介紹的非常詳細，對大家的學習或者工作具有一定的參考學習價值，需要的朋友們下面隨著小編來一起學習學習吧2023-07-07
這篇文章主要介紹了Redis開啟遠程訪問及密碼的教程，文中給大家提到了Redis啟動報錯解決方法,需要的朋友可以參考下2019-10-10