redis-cluster 報錯 CLUSTERDOWN Hash slot not served 的解決辦法
問題示例:
(base) wdh@wdh:~/D/nmpr$ redis-cli -c -h 172.17.0.1 -p 6379
172.17.0.1:6379> set name wdh
(error) CLUSTERDOWN Hash slot not served
172.17.0.1:6379> quit
解決辦法:
- 1.可能是redis節點沒有全部加入到到集羣中。連接每一個集羣節點meet集羣。
例如,我的集羣節點如下:
cluster:172.17.0.1 6379
master1:172.17.0.1 6391
master2:172.17.0.1 6392
master3:172.17.0.1 6393
slave1:172.17.0.1 6391
slave2:172.17.0.1 6392
slave3:172.17.0.1 6393
那麼用reids-cli命令鏈接redis各節點,並依次meet集羣入口6379之後,集羣即可恢復正常:
redis-cli -c -h 172.17.0.1 -p 6391
>cluster meet 172.17.0.1 6379
>quit
redis-cli -c -h 172.17.0.1 -p 6392
>cluster meet 172.17.0.1 6379
>quit
redis-cli -c -h 172.17.0.1 -p 6393
>cluster meet 172.17.0.1 6379
>quit
redis-cli -c -h 172.17.0.1 -p 6394
>cluster meet 172.17.0.1 6379
>quit
redis-cli -c -h 172.17.0.1 -p 6395
>cluster meet 172.17.0.1 6379
>quit
執行結果:
(base) wdh@wdh-PC:~$ docker exec -it redis-master1 /bin/bash
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6396
172.50.0.1:6396> cluster meet 172.17.0.1 6379
OK
172.50.0.1:6396> quit
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6395
172.17.0.1:6395> cluster meet 172.17.0.1 6379
OK
172.17.0.1:6395> quit
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6394
172.17.0.1:6394> cluster meet 172.17.0.1 6379
OK
172.17.0.1:6394> quit
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6393
172.17.0.1:6393> cluster meet 172.17.0.1 6379
OK
172.17.0.1:6393> quit
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6392
172.17.0.1:6392> cluster meet 172.17.0.1 6379
OK
172.17.0.1:6392> quit
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6391
172.17.0.1:6391> cluster meet 172.17.0.1 6379
OK
172.17.0.1:6391>
- 其他方法參考(我沒有驗證這些方法是否可行):
標題:redis-cluster遇到CLUSTERDOWN Hash slot not served問題
地址:https://www.jianshu.com/p/e519471d530b
標題:解決 (error) CLUSTERDOWN Hash slot not served
地址:https://blog.csdn.net/u010235716/article/details/99645657
標題:(error) CLUSTERDOWN Hash slot not served
地址:https://blog.csdn.net/u012060033/article/details/78553124
標題:redis集羣報錯:(error) CLUSTERDOWN Hash slot not served
地址:https://www.cnblogs.com/hanguoqing/p/10411128.html
測試是否已解決:
# 連接一個redis節點(我這裏連接了master1),執行:redis-cli -c -h 172.17.0.1 -p 6392 然後設置一個數據:set name wdh
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6392
172.17.0.1:6392> set name wdh
OK
172.17.0.1:6392>
# 連接另一個 redis節點,執行:redis-cli -c -h 172.17.0.1 -p 6396 然後讀取第一個節點設置的數據:get name wdh
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6396
172.17.0.1:6396> get name
-> Redirected to slot [5798] located at 172.50.0.1:6392
"wdh"
172.50.0.1:6392>
# 然後redis連接集羣(172.17.0.1 6379):redis-cli -c -h 172.17.0.1 -p 6379,然後測試讀取集羣讀寫在節點中的設置的數據
(base) wdh@wdh-PC:~/nmpr/redis$ redis-cli -c -h 172.17.0.1 -p 6379
172.100.0.3:6392> get name
"wdh"
172.100.0.3:6392>
# 成功讀到節點中的數據
# 測試寫入數據:
172.100.0.3:6392> set sex 1
-> Redirected to slot [2584] located at 172.100.0.1:6391
OK
172.100.0.1:6391>
# 測試去單個節點讀取:
root@306117aceb78:/config# redis-cli -c -h 172.17.0.1 -p 6394
172.17.0.1:6394> get sex
-> Redirected to slot [2584] located at 172.50.0.1:6391
"1"
172.50.0.1:6391>
# 以上結果證明一切都 OK