[ERR] Node 192.168.4.57:6357 is not empty. Either the node already knows other nodes (check with CLU

最新推荐文章于 2022-04-08 10:02:04 发布
最新推荐文章于 2022-04-08 10:02:04 发布
阅读量1.6k 收藏
点赞数
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zhydream77/article/details/80914984
版权

原因主要是原有的添加在redis配置中，没有进行重置之前的配置

[root@host57 ~]# redis-cli -h 192.168.4.57 -p 6357 
192.168.4.57:6357> CLUSTER RESET
OK
192.168.4.57:6357> cluster info
cluster_state:fail
cluster_slots_assigned:0
cluster_slots_ok:0
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:1
cluster_size:0
cluster_current_epoch:9
cluster_my_epoch:8
cluster_stats_messages_ping_sent:32
cluster_stats_messages_pong_sent:7
cluster_stats_messages_sent:39
cluster_stats_messages_ping_received:7
cluster_stats_messages_pong_received:32
cluster_stats_messages_received:39


管理服务器
[root@51 ~]# redis-trib.rb add-node   192.168.4.57:6357  192.168.4.51:6351
>>> Adding node 192.168.4.57:6357 to cluster 192.168.4.51:6351
>>> Performing Cluster Check (using node 192.168.4.51:6351)
M: b00bfb1d93247f56719582e8b9865ae374e17c33 192.168.4.51:6351
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: 2f002d4ec870d72d2f966c6051a586c57cff1afa 192.168.4.52:6352
   slots: (0 slots) slave
   replicates 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a
M: 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a 192.168.4.56:6356
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
S: 0ba5e235aa72f9ea10ed8f7da1a60caefc9b9b6c 192.168.4.55:6355
   slots: (0 slots) slave
   replicates b00bfb1d93247f56719582e8b9865ae374e17c33
M: 45f61b35eaf179a4b161008b79c54122617048ee 192.168.4.53:6353
   slots:0-1364,5461-6826,10923-16383 (8192 slots) master
   1 additional replica(s)
S: 9672778d5a8c6685daa7339df325d93f6c73b6bd 192.168.4.54:6354
   slots: (0 slots) slave
   replicates 45f61b35eaf179a4b161008b79c54122617048ee
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.4.57:6357 to make it join the cluster.
[OK] New node added correctly.


[root@51 ~]# redis-trib.rb check 192.168.4.51:6351
>>> Performing Cluster Check (using node 192.168.4.51:6351)
M: b00bfb1d93247f56719582e8b9865ae374e17c33 192.168.4.51:6351
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
M: 6df9172d2b03bf298dc7342acdcf1b385f367aba 192.168.4.57:6357
   slots: (0 slots) master
   0 additional replica(s)
S: 2f002d4ec870d72d2f966c6051a586c57cff1afa 192.168.4.52:6352
   slots: (0 slots) slave
   replicates 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a
M: 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a 192.168.4.56:6356
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
S: 0ba5e235aa72f9ea10ed8f7da1a60caefc9b9b6c 192.168.4.55:6355
   slots: (0 slots) slave
   replicates b00bfb1d93247f56719582e8b9865ae374e17c33
M: 45f61b35eaf179a4b161008b79c54122617048ee 192.168.4.53:6353
   slots:0-1364,5461-6826,10923-16383 (8192 slots) master
   1 additional replica(s)
S: 9672778d5a8c6685daa7339df325d93f6c73b6bd 192.168.4.54:6354
   slots: (0 slots) slave
   replicates 45f61b35eaf179a4b161008b79c54122617048ee
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.






[root@host57 ~]# redis-cli -h 192.168.4.57 -p 6357 
192.168.4.57:6357> CLUSTER RESET
OK


192.168.4.57:6357> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:7
cluster_size:3
cluster_current_epoch:9
cluster_my_epoch:8
cluster_stats_messages_ping_sent:1230
cluster_stats_messages_pong_sent:587
cluster_stats_messages_meet_sent:6
cluster_stats_messages_sent:1823
cluster_stats_messages_ping_received:587
cluster_stats_messages_pong_received:1236
cluster_stats_messages_received:1823

把移除的主机在此添加到原有的集群中

[root@host57 ~]# redis-cli -h 192.168.4.57 -p 6357 
192.168.4.57:6357> CLUSTER RESET
OK
192.168.4.57:6357> cluster info
cluster_state:fail
cluster_slots_assigned:0
cluster_slots_ok:0
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:1
cluster_size:0
cluster_current_epoch:9
cluster_my_epoch:8
cluster_stats_messages_ping_sent:32
cluster_stats_messages_pong_sent:7
cluster_stats_messages_sent:39
cluster_stats_messages_ping_received:7
cluster_stats_messages_pong_received:32
cluster_stats_messages_received:39


管理服务器
[root@51 ~]# redis-trib.rb add-node   192.168.4.57:6357  192.168.4.51:6351
>>> Adding node 192.168.4.57:6357 to cluster 192.168.4.51:6351
>>> Performing Cluster Check (using node 192.168.4.51:6351)
M: b00bfb1d93247f56719582e8b9865ae374e17c33 192.168.4.51:6351
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
S: 2f002d4ec870d72d2f966c6051a586c57cff1afa 192.168.4.52:6352
   slots: (0 slots) slave
   replicates 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a
M: 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a 192.168.4.56:6356
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
S: 0ba5e235aa72f9ea10ed8f7da1a60caefc9b9b6c 192.168.4.55:6355
   slots: (0 slots) slave
   replicates b00bfb1d93247f56719582e8b9865ae374e17c33
M: 45f61b35eaf179a4b161008b79c54122617048ee 192.168.4.53:6353
   slots:0-1364,5461-6826,10923-16383 (8192 slots) master
   1 additional replica(s)
S: 9672778d5a8c6685daa7339df325d93f6c73b6bd 192.168.4.54:6354
   slots: (0 slots) slave
   replicates 45f61b35eaf179a4b161008b79c54122617048ee
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.
>>> Send CLUSTER MEET to node 192.168.4.57:6357 to make it join the cluster.
[OK] New node added correctly.


[root@51 ~]# redis-trib.rb check 192.168.4.51:6351
>>> Performing Cluster Check (using node 192.168.4.51:6351)
M: b00bfb1d93247f56719582e8b9865ae374e17c33 192.168.4.51:6351
   slots:1365-5460 (4096 slots) master
   1 additional replica(s)
M: 6df9172d2b03bf298dc7342acdcf1b385f367aba 192.168.4.57:6357
   slots: (0 slots) master
   0 additional replica(s)
S: 2f002d4ec870d72d2f966c6051a586c57cff1afa 192.168.4.52:6352
   slots: (0 slots) slave
   replicates 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a
M: 20b20d6ddf38a67e8f81bb7badec220bf2be7b3a 192.168.4.56:6356
   slots:6827-10922 (4096 slots) master
   1 additional replica(s)
S: 0ba5e235aa72f9ea10ed8f7da1a60caefc9b9b6c 192.168.4.55:6355
   slots: (0 slots) slave
   replicates b00bfb1d93247f56719582e8b9865ae374e17c33
M: 45f61b35eaf179a4b161008b79c54122617048ee 192.168.4.53:6353
   slots:0-1364,5461-6826,10923-16383 (8192 slots) master
   1 additional replica(s)
S: 9672778d5a8c6685daa7339df325d93f6c73b6bd 192.168.4.54:6354
   slots: (0 slots) slave
   replicates 45f61b35eaf179a4b161008b79c54122617048ee
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.






[root@host57 ~]# redis-cli -h 192.168.4.57 -p 6357 
192.168.4.57:6357> CLUSTER RESET
OK


192.168.4.57:6357> cluster info
cluster_state:ok
cluster_slots_assigned:16384
cluster_slots_ok:16384
cluster_slots_pfail:0
cluster_slots_fail:0
cluster_known_nodes:7
cluster_size:3
cluster_current_epoch:9
cluster_my_epoch:8
cluster_stats_messages_ping_sent:1230
cluster_stats_messages_pong_sent:587
cluster_stats_messages_meet_sent:6
cluster_stats_messages_sent:1823
cluster_stats_messages_ping_received:587
cluster_stats_messages_pong_received:1236
cluster_stats_messages_received:1823
zhy-dream
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
node.js -v16.20.2
11-08
 mv node-v16.20.2-linux-x64 node  sudo -s  cp -a /data1/tempobi/tempo/mids/node/bin/node /usr/local/bin/node  cp -a /data1/tempobi/tempo/mids/node/bin/npm /usr/local/bin/npm
node.js请求HTTPS报错：UNABLE_TO_VERIFY_LEAF_SIGNATURE\的解决方法
11-28
发现错误 ... events.js:72 throw er; // Unhandled \'error\' event ^ Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE at SecurePair....at SecurePair.emit (events.js:92:17) at SecurePair.maybeInitFinished (tls.js:980:10...
Node 192.168.248.12:7001 is not empty. Either the node already knows other nodes (check with CLUSTER...
weixin_30954607的博客
12-02 619
[root@node00 src]#./redis-trib.rb add-node --slave --master-id4f6424e47a2275d2b7696bfbf8588e8c4c3a5b95 172.168.63.202:7001172.168.63.202:7000 ...... [OK] All nodes agree about slotsconfiguration...
[ERR] Node is not empty. Either the node already knows other nodes (check with C
热门推荐
漫天雪_昆仑巅
12-09 26万+
最近在给公司网管系统redis集群环境添加节点时候遇到一个问题，提示新增的Node不为空： [root@node00 src]# ./redis-trib.rb add-node --slave --master-id4f6424e47a2275d2b7696bfbf8588e8c4c3a5b95 172.168.63.202:7001172.168.63.202:7000 .....
[ERR] Node 192.168.245.111:6379 is not empty. Either the node already knows other nodes (check with
weixin_42382758的博客
04-08 4367
报错信息：[ERR] Node 192.168.245.111:6379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 背景：第二天启动redis集群就报错（第一天正常工作，然后关机） 原因: 可能是非正常关闭集群导致 1-数据清空 flushdb命令清除所有节点中（我的是6个节点，3主3从）的数据 ..
[ERR] Node xxxxx is not empty. Either the node already knows other nodes (check with CLUSTER NODES)
one312的专栏
03-20 1876
问题示例： 执行创建redis集群命令时， # 我这里ip都是172.17.0.1是因为我这里的redis节点都是docker容器，每个容器都已经映射到了主机172.17.0.1的不同端口 redis-cli --cluster create 172.17.0.1:6391 172.17.0.1:6392 172.17.0.1:6393 172.17.0.1:6394 172.17.0.1:639...
解决[ERR] Node xxx is not empty. Either the node already knows other nodes (check with CLUSTER NODES)
weixin_44093711的博客
04-24 2454
解决： [ERR] Node 192.168.114.100:7001 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 我是将 每个节点下的两个文件删除掉 然后依次执行，最后创建集群发现成功！！ ...
Node.js：开启全栈开发的钥匙.pdf
最新发布
07-25
### Node.js：开启全栈开发的钥匙 #### 一、Node.js 基础概述 ##### 1.1 Node.js 是什么？ Node.js 是一种基于 Chrome V8 JavaScript 引擎的运行环境，允许开发者在服务器端运行 JavaScript。与传统服务器端语言...
数据库疑难杂症 java.sql.SQLSyntaxErrorException: You have an error in your SQL syntax; check the manual tha
12-14
check the manual that corresponds to your MySQL server version for the right syntax to use near ‘order’ at line 1 数据库报错如下： Error querying database. Cause: java.sql.SQLSyntaxErrorException: ...
resolve：实现node.js require.resolve（）算法
02-02
/home/substack/projects/node-resolve/node_modules/tap/lib/main.js 同步解决： var resolve = require ( 'resolve' ) ; var res = resolve . sync ( 'tap' , { basedir : __dirname } ) ; console . log ( res )...
is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some
weixin_41299767的博客
02-09 1821
运行 ./redis-cli --cluster create 10.9.112.118:7001 10.9.112.119:7003 10.9.98.169:7005 10.9.112.118:7002 10.9.112.119:7004 10.9.98.169:7006 --cluster-replicas 1，报以下错误 解决方法： 1)、将需要新增的节点下aof、rdb等本地备份文件删除； 2)、同时将新Node的集群配置文件删除,即：删除你redis.conf里面cluster-
Redis+阿里云远程连接
GongRuiFeng1992的博客
11-22 253
1.redis.conf,修改ip127.0.0.1为0.0.0.0 2.ps -ef | grep redis,  kill -9 ID  3.重启redis服务 4.vi etc/sysconfig/iptabls，增加当前redis端口 5.service iptables retart 6.阿里云安全组增加开放此端口 done!...
redis集群启动时报[ERR] Node x.x.xx:x is not empty. Either the node already knows other nodes (check ... ..
weixin_44316575的博客
03-21 391
redis集群在主机宕机后再次启动集群会报一个错误，如下图。 >>> Creating cluster [ERR] Node x.x.x.x:xis not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database...
redis创建集群时显示错误： [ERR] Node xxx is not empty. Either the node already knows other no...
Lewis的博客
11-09 1617
一、问题 在redis集群配置的最后一步，使用命令报错：[ERR] Node xxx.xxx.xxx.xxx:7004 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 二、解决方法 1、删除每个redis节点的备份文件，数据库文件和集群配置文件 比如说我有7001~7006 6个节点，那么每个节点中的appen
添加redis 节点报错[ERR] Node 127.0.0.1:6002 is not empty. Either the node already knows other nodes (check
司马缸砸缸了
05-07 9257
出错： [ERR] Node 127.0.0.1:6002 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 找了1个多小时的错误，搞得人好无奈。 解决方法： 删除nodes-xxx.conf配置...
[ERR] Node is not empty. Either the node already knows other nodes (check with C
斗鹰的技术专栏
10-18 4836
搭建redis集群整合出现问题： >>> Creating cluster[ERR] Node 192.168.211.128:6379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0....
Node 192.168.248.12:7001 is not empty. Either the node already knows other nodes解决办法
xinyuanjieyiwife的博客
11-09 2898
在启动创建好的redis集群时 执行./redis-cli --cluster create ip:端口 报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.错误 解决办法： 1，先kill redis创建的集群节点进程 2，删除每个redis节点的appe
redis集群服务器迁移报错[ERR] Node XXX.XXX.XXX.XX:7001 is not empty. Either the nodealready knows other nodes
wanzuwodou的博客
07-21 1139
redis迁移服务器报节点错误： [ERR] Node XXX.XXX.XXX.XX:7001 is not empty. Either the nodealready knows other nodes (check with CLUSTER NODES) or contains some 解决方法如下： 1)检查新部署的服务器的ruby环境。
redis集群添加节点报错Either the node already knows other nodes (check with CLUSTER NODES) or contains some k
PacosonSWJTU的博客
02-18 7869
【README】 redis集群添加节点报错 [ERR] Node 192.168.163.202:6380 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0. 【1】 原因 导致异常的主要原因是该节点中默认生成的配置或历史存储数据不一致导致的，清除对应节点的dump.rdb、nodes.conf文件，重启之后即可..
./src/redis-cli -a Sftw@2023 --cluster create 10.17.75.221:16379 10.17.75.227:16379 10.17.75.230:16379 10.17.75.221:16380 10.17.75.227:16380 10.17.75.230:16380 --cluster-replicas 1 Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe. [ERR] Node 10.17.75.221:16379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.
07-15
根据你提供的命令，使用redis-cli创建Redis集群时出现了两个问题。 第一个问题是关于密码的警告信息：`Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.` 这个警告表示在命令行接口上使用密码选项 `-a` 可能不安全。为了更安全地传递密码，你可以使用Redis配置文件或者环境变量来指定密码。 第二个问题是关于节点 `10.17.75.221:16379` 的错误信息：`[ERR] Node 10.17.75.221:16379 is not empty. Either the node already knows other nodes (check with CLUSTER NODES) or contains some key in database 0.` 这个错误表示节点 `10.17.75.221:16379` 不为空，可能已经知道其他节点或者在数据库0中包含一些键。 为了解决这些问题，你可以尝试以下步骤： 1. 避免在命令行接口上直接传递密码。你可以在Redis配置文件中设置密码，或者通过环境变量来传递密码。 2. 在继续创建集群之前，确保节点 `10.17.75.221:16379` 是一个空节点。你可以使用以下命令检查节点的状态： ``` ./src/redis-cli -a <password> -h 10.17.75.221 -p 16379 CLUSTER NODES ``` 这将显示节点的状态信息。如果该节点已经知道其他节点或者在数据库0中包含键，你需要清空节点或者选择一个空节点来创建集群。 如果该节点是一个新节点并且没有包含任何键，你可以尝试移除该节点的数据文件，然后再次尝试创建集群。 请注意，以上步骤可能需要一定的技术知识和操作权限。如果你不确定如何执行这些步骤，建议联系Redis管理员或者查阅相关文档以获取更多帮助和支持。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值