Windows下部署redis主從、哨兵（sentinel）、集羣（cluster）

準備工作

1.下載redis文件：https://github.com/MicrosoftArchive/redis/releases（windows版本已經不更新了，最新版就是3.2.100，我本地用的是3.0.501）
2.下載Ruby安裝文件：https://rubyinstaller.org/downloads/（最新版本是3.0.0-1，我下載的是2.7.2-1（x64））
3.下載Ruby環境下Redis的驅動：https://rubygems.org/gems/redis/versions/3.2.2，考慮到兼容性，這裏下載的是3.2.2版本
注意：下載在頁面右下角相關連接一項中
4.下載Redis官方提供的創建Redis集羣的ruby腳本文件redis-trib.rb，路徑如下：https://raw.githubusercontent.com/MSOpenTech/redis/3.0/src/redis-trib.rb（全選文本複製下來，存到ruby安裝目錄下）

Redis主從

1.把下載的redis安裝包解壓，
2. 複製2份redis.windows.conf配置文件，分別命名爲redis.windows6380.conf和redis.windows6381.conf
3. 修改配置

redis.windows6380.conf如下：
port 6380
bind 127.0.0.1
slaveof 127.0.0.1 6379 // 設置master服務器爲6379，如果不寫這一段，也可以啓動服務後，在連上服務器後執行slaveof 127.0.0.1 6379

redis.windows6381.conf如下：
port 6381
bind 127.0.0.1
slaveof 127.0.0.1 6379 // 設置master服務器爲6379

4.啓動服務

在redis安裝目錄下執行命令
redis-server.exe redis.windows.conf
redis-server.exe redis.windows6380.conf
redis-server.exe redis.windows6381.con

5.查看主從
redis-cli -h 127.0.0.1 -p 6380 連接6380redis服務
info Replication 查看主從信息

# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:11056
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

注意：從節點只讀

Redis哨兵（sentinel）

1.和上面主從一樣啓動6379、6380、6381三個服務
2.創建sentinel26379.conf文件，然後複製兩份sentinel26380.conf、sentinel26381.conf
sentinel26379.conf文件內容

port 26379
#下面兩行註釋掉了，是因爲低版本redis不支持這兩個命令
#sentinel myid fad25e089080be8dddadd3f20e44f888b1f8d48a
#sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 15000

sentinel26380.conf文件內容

port 26380
#下面兩行註釋掉了，是因爲低版本redis不支持這兩個命令
#sentinel myid fad25e089080be8dddadd3f20e44f888b1f8d48b
#sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 15000

sentinel26381.conf文件內容

port 26381
#下面兩行註釋掉了，是因爲低版本redis不支持這兩個命令
#sentinel myid fad25e089080be8dddadd3f20e44f888b1f8d48c
#sentinel deny-scripts-reconfig yes
sentinel monitor mymaster 127.0.0.1 6379 2
sentinel down-after-milliseconds mymaster 10000
sentinel failover-timeout mymaster 15000

如果報下面的錯，註釋掉sentinel myid即可

D:\install\redis>redis-server.exe sentinel26379.conf --sentinel
Invalid argument during startup: Could not find sentinal subcommand myid

3.啓動哨兵服務

redis-server.exe sentinel26379.conf --sentinel
redis-server.exe sentinel26380.conf --sentinel
redis-server.exe sentinel26381.conf --sentinel

4.關閉6379服務，查看主從變化
6379沒關閉之前，在6380服務看master是6379

127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6379
master_link_status:down
master_last_io_seconds_ago:-1
slave_repl_offset:36508
master_link_down_since_seconds:jd
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

關閉6379之後，可以看到master自動變成6381了

127.0.0.1:6380> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6381
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:836
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

這個時候再重新啓動6379,6379會自動變成6381的slave

D:\install\redis> redis-cli.exe -h 127.0.0.1 -p 6379
127.0.0.1:6379> info replication
# Replication
role:slave
master_host:127.0.0.1
master_port:6381
master_link_status:up
master_last_io_seconds_ago:0
master_sync_in_progress:0
slave_repl_offset:20949
slave_priority:100
slave_read_only:1
connected_slaves:0
master_repl_offset:0
repl_backlog_active:0
repl_backlog_size:1048576
repl_backlog_first_byte_offset:0
repl_backlog_histlen:0

Redis集羣（cluster）

1.安裝ruby環境
雙擊下載的“rubyinstaller-2.7.2-1-x64.exe”安裝即可，同樣，爲了操作方便，也是建議安裝在盤符根目錄下，如： C:\Ruby27-x64 ，安裝會默認把ruby添加到path環境變量
2.安裝Ruby環境下Redis的驅動
將下載的"Ruby環境下Redis的驅動文件(redis-3.2.2.gem)"拷貝到Ruby安裝根目錄（C:\Ruby27-x64）下。
然後執行安裝命令如下：

gem install --local C:/Ruby27-x64/redis-3.2.2.gem

3.將下載的“創建Redis集羣的ruby腳本文件redis-trib.rb”文件拷貝到Redis安裝根目錄(D:\install\redis)下。
4.新建配置文件redis.windows-service-6380.conf

port 6380      
loglevel notice    
logfile "D:/install/redis/Logs/redis6380_log.txt"       
appendonly yes
appendfilename "appendonly.6380.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6380.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

複製5份
redis.windows-service-6381.conf

port 6381      
loglevel notice    
logfile "D:/install/redis/Logs/redis6381_log.txt"       
appendonly yes
appendfilename "appendonly.6381.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6381.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

redis.windows-service-6382.conf

port 6382      
loglevel notice    
logfile "D:/install/redis/Logs/redis6382_log.txt"       
appendonly yes
appendfilename "appendonly.6382.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6382.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

redis.windows-service-6383.conf

port 6383      
loglevel notice    
logfile "D:/install/redis/Logs/redis6383_log.txt"       
appendonly yes
appendfilename "appendonly.6383.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6383.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

redis.windows-service-6384.conf

port 6384      
loglevel notice    
logfile "D:/install/redis/Logs/redis6384_log.txt"       
appendonly yes
appendfilename "appendonly.6384.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6384.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

redis.windows-service-6385.conf

port 6385      
loglevel notice    
logfile "D:/install/redis/Logs/redis6385_log.txt"       
appendonly yes
appendfilename "appendonly.6385.aof"   
cluster-enabled yes                                    
cluster-config-file nodes.6385.conf
cluster-node-timeout 15000
cluster-slave-validity-factor 10
cluster-migration-barrier 1
cluster-require-full-coverage yes

配置解釋如下：

 1 port 6380                                 #端口號
 2 loglevel notice                           #日誌的記錄級別，notice是適合生產環境的
 3 logfile "Logs/redis6380_log.txt"          #指定log的保持路徑,默認是創建在Redis安裝目錄下，如果有子目錄需要手動創建，如此處的Logs目錄
 4 syslog-enabled yes                        #是否使用系統日誌
 5 syslog-ident redis6380                    #在系統日誌的標識名
 6 appendonly yes                            #數據的保存爲aof格式
 7 appendfilename "appendonly.6380.aof"      #數據保存文件
 8 cluster-enabled yes                       #是否開啓集羣
 9 cluster-config-file nodes.6380.conf
10 cluster-node-timeout 15000
11 cluster-slave-validity-factor 10
12 cluster-migration-barrier 1
13 cluster-require-full-coverage yes

5.啓動上面6個redis服務

redis-server.exe redis.windows-service-6380.conf
redis-server.exe redis.windows-service-6381.conf
redis-server.exe redis.windows-service-6382.conf
redis-server.exe redis.windows-service-6383.conf
redis-server.exe redis.windows-service-6384.conf
redis-server.exe redis.windows-service-6385.conf

6.執行創建集羣命令
redis-trib.rb create --replicas 1 127.0.0.1:6380 127.0.0.1:6381 127.0.0.1:6382 127.0.0.1:6383 127.0.0.1:6384 127.0.0.1:6385

D:\install\redis>redis-trib.rb create --replicas 1 127.0.0.1:6380 127.0.0.1:6381 127.0.0.1:6382 127.0.0.1:6383 127.0.0.1:6384 127.0.0.1:6385
>>> Creating cluster
Connecting to node 127.0.0.1:6380: OK
Connecting to node 127.0.0.1:6381: OK
Connecting to node 127.0.0.1:6382: OK
Connecting to node 127.0.0.1:6383: OK
Connecting to node 127.0.0.1:6384: OK
Connecting to node 127.0.0.1:6385: OK
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
127.0.0.1:6380
127.0.0.1:6381
127.0.0.1:6382
Adding replica 127.0.0.1:6383 to 127.0.0.1:6380
Adding replica 127.0.0.1:6384 to 127.0.0.1:6381
Adding replica 127.0.0.1:6385 to 127.0.0.1:6382
M: db4712669500b212790e01e0f3761b30417b1fa9 127.0.0.1:6380
   slots:0-5460 (5461 slots) master
M: af81b3ec8883758a441c277b251477777cf95331 127.0.0.1:6381
   slots:5461-10922 (5462 slots) master
M: 59fd4bf6813665ed781e066a343717d2a0833729 127.0.0.1:6382
   slots:10923-16383 (5461 slots) master
S: bd8addd7b86d6e5d178c66b5441e5ace8b2e67ee 127.0.0.1:6383
   replicates db4712669500b212790e01e0f3761b30417b1fa9
S: 331c145eb0527a93d2e6a4d52b781b039ddf4b0a 127.0.0.1:6384
   replicates af81b3ec8883758a441c277b251477777cf95331
S: a7e8e30b8a70b4eee28523fa56e516edfbeee385 127.0.0.1:6385
   replicates 59fd4bf6813665ed781e066a343717d2a0833729
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 127.0.0.1:6380)
M: db4712669500b212790e01e0f3761b30417b1fa9 127.0.0.1:6380
   slots:0-5460 (5461 slots) master
M: af81b3ec8883758a441c277b251477777cf95331 127.0.0.1:6381
   slots:5461-10922 (5462 slots) master
M: 59fd4bf6813665ed781e066a343717d2a0833729 127.0.0.1:6382
   slots:10923-16383 (5461 slots) master
M: bd8addd7b86d6e5d178c66b5441e5ace8b2e67ee 127.0.0.1:6383
   slots: (0 slots) master
   replicates db4712669500b212790e01e0f3761b30417b1fa9
M: 331c145eb0527a93d2e6a4d52b781b039ddf4b0a 127.0.0.1:6384
   slots: (0 slots) master
   replicates af81b3ec8883758a441c277b251477777cf95331
M: a7e8e30b8a70b4eee28523fa56e516edfbeee385 127.0.0.1:6385
   slots: (0 slots) master
   replicates 59fd4bf6813665ed781e066a343717d2a0833729
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.

7.查看集羣

D:\install\redis>redis-trib.rb check 127.0.0.1:6380
Connecting to node 127.0.0.1:6380: OK
Connecting to node 127.0.0.1:6385: OK
Connecting to node 127.0.0.1:6384: OK
Connecting to node 127.0.0.1:6381: OK
Connecting to node 127.0.0.1:6383: OK
*** WARNING: 127.0.0.1:6385 claims to be slave of unknown node ID 59fd4bf6813665ed781e066a343717d2a0833729.
>>> Performing Cluster Check (using node 127.0.0.1:6380)
M: db4712669500b212790e01e0f3761b30417b1fa9 127.0.0.1:6380
   slots:0-5460 (5461 slots) master
   1 additional replica(s)
S: a7e8e30b8a70b4eee28523fa56e516edfbeee385 127.0.0.1:6385
   slots: (0 slots) slave
   replicates 59fd4bf6813665ed781e066a343717d2a0833729
S: 331c145eb0527a93d2e6a4d52b781b039ddf4b0a 127.0.0.1:6384
   slots: (0 slots) slave
   replicates af81b3ec8883758a441c277b251477777cf95331
M: af81b3ec8883758a441c277b251477777cf95331 127.0.0.1:6381
   slots:5461-10922 (5462 slots) master
   1 additional replica(s)
S: bd8addd7b86d6e5d178c66b5441e5ace8b2e67ee 127.0.0.1:6383
   slots: (0 slots) slave
   replicates db4712669500b212790e01e0f3761b30417b1fa9
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[ERR] Not all 16384 slots are covered by nodes.

8.執行redis命令
如集羣連接需要加-c，不然get key的時候會報錯
(error) MOVED 6340 127.0.0.1:6381

redis-cli -c -h 127.0.0.1 -p 6380

redis目錄結構

參考文章

https://www.cnblogs.com/yy3b2007com/p/11033009.html
https://www.cnblogs.com/justdoyou/p/10253668.html