碼上快樂

相關內容    簡體    繁體

redis服務在宕機之后報錯“Node xxxx:7000 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0”（windows）

本文轉載自   查看原文   2018-08-17 15:56   3239    redis

redis在啟動集群時報錯，xxxx:7000 is not empty. Either the node already knows other nodes(check with CLUSTER NODES) or contains some key in database 0”

 

解決方案：

1、刪除redis啟動集群時生成的.aof文件和.rdb文件；

2、將對應節點的“nodes-7000.conf”文件（在redis.windows.config文件的“cluster-config-file nodes-7000.conf”位置處配置）刪除

3、重新執行“redis-trib.rb create --replicas 1 xxxx:7000 xxxx:7001 xxxx:7002 xxxx:7003 xxxx:7004 xxxx:7005”，啟動集群成功

 

aof和rdb是兩個可持久化文件，一般可用來做數據恢復

 

aof比rdb在可靠性上更高一些

 


免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。



猜您在找 Node 192.168.248.12:7001 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. [ERR] Node 172.168.63.202:7001 is not empty. Either the nodealready knows other nodes (check with CLUSTER NODES) or contains some redis學習之集群報錯Node is not empty cluster nodes命令 lua腳本在redis集群中執行報錯--Lua script attempted to access a non local key in a cluster node maybe these locations are not writable or multiple nodes were started without increasing [node.max_local_storage_nodes] (was [1])? 解決報錯Could not satisfy explicit device specification '' because the node was colocated with a group of nodes that required incompatible device '/device:GPU:0' yarn查詢/cluster/nodes均返回localhost 0/1 nodes are available: 1 node(s) had taint {node-role.kubernetes.io/master: } error: inner element must either be a resource reference or empty.
 
粵ICP備18138465號   © 2018-2025 CODEPRJ.COM