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） - 码上快乐

相关内容简体繁体

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