创建redis集群出错：Invalid IP or Port (given as replicas) - use IP:Port format

最新推荐文章于 2023-10-09 11:19:45 发布

原创最新推荐文章于 2023-10-09 11:19:45 发布 · 3.9k 阅读

3 ·

CC 4.0 BY-SA版权

文章标签：

#redis #缓存 #redis缓存集群 #高可用 #高并发

redis 专栏收录该内容

2 篇文章

订阅专栏

本文详细记录了在创建Redis集群过程中遇到的“InvalidIPorPort”错误及其解决方法，强调了正确使用参数的重要性。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

今天在创建redis 集群时报错：Invalid IP or Port (given as replicas) - use IP:Port format
这是因为大意造成的，这里做一下记录。。。方便以后查阅

造成问题的操作如下：
安装了redis/ruby等程序后，并将redis启动了（共8个redis），使用创建群集的代码如下：

[root@localhost redis-cluster]# /java_software/redis-cluster/redis-trib.rb create replicas 1 192.168.8.134:6701 192.168.8.134:6702 192.168.8.134:6703 192.168.8.134:6704 192.168.8.134:6705 192.168.8.134:6706 192.168.8.134:6707 192.168.8.134:6708
>>> Creating cluster
Invalid IP or Port (given as replicas) - use IP:Port format

问题出现了。。。仔细查看了一下代码，发现是因为参数写错造成的，

replicas 改为 --replicas

修改后再次执行：

[root@localhost redis-cluster]# ./redis-trib.rb create --replicas 1 192.168.8.134:6701 192.168.8.134:6702 192.168.8.134:6703 192.168.8.134:6704 192.168.8.134:6705 192.168.8.134:6706 192.168.8.134:6707 192.168.8.134:6708

执行效果如下：

>>> Performing hash slots allocation on 8 nodes...
Using 4 masters:
192.168.8.134:6701
192.168.8.134:6702
192.168.8.134:6703
192.168.8.134:6704
Adding replica 192.168.8.134:6705 to 192.168.8.134:6701
Adding replica 192.168.8.134:6706 to 192.168.8.134:6702
Adding replica 192.168.8.134:6707 to 192.168.8.134:6703
Adding replica 192.168.8.134:6708 to 192.168.8.134:6704
M: 0951918d05ab6e9111f89583765b1e911e9a47d5 192.168.8.134:6701
   slots:0-4095 (4096 slots) master
M: e827eafabf2901dcee8bdfbd096427574fced219 192.168.8.134:6702
   slots:4096-8191 (4096 slots) master
M: 77dc0f02db99b74735c5d76aef3a244cfdceef7a 192.168.8.134:6703
   slots:8192-12287 (4096 slots) master
M: 56af1ba41b71c86f0e808078cd5ebb4acbe7fa77 192.168.8.134:6704
   slots:12288-16383 (4096 slots) master
S: ca41d169c0002155df817560f1474174e29150d7 192.168.8.134:6705
   replicates 0951918d05ab6e9111f89583765b1e911e9a47d5
S: 70115c6f223a518e7822a224d45348dc52779433 192.168.8.134:6706
   replicates e827eafabf2901dcee8bdfbd096427574fced219
S: c4e22dc80492bd0b28830e689de6301a23f4efdb 192.168.8.134:6707
   replicates 77dc0f02db99b74735c5d76aef3a244cfdceef7a
S: 5d1abd29c8902d2c53ecff3d65cb95adc6ad6b25 192.168.8.134:6708
   replicates 56af1ba41b71c86f0e808078cd5ebb4acbe7fa77
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 192.168.8.134:6701)
M: 0951918d05ab6e9111f89583765b1e911e9a47d5 192.168.8.134:6701
   slots:0-4095 (4096 slots) master
M: e827eafabf2901dcee8bdfbd096427574fced219 192.168.8.134:6702
   slots:4096-8191 (4096 slots) master
M: 77dc0f02db99b74735c5d76aef3a244cfdceef7a 192.168.8.134:6703
   slots:8192-12287 (4096 slots) master
M: 56af1ba41b71c86f0e808078cd5ebb4acbe7fa77 192.168.8.134:6704
   slots:12288-16383 (4096 slots) master
M: ca41d169c0002155df817560f1474174e29150d7 192.168.8.134:6705
   slots: (0 slots) master
   replicates 0951918d05ab6e9111f89583765b1e911e9a47d5
M: 70115c6f223a518e7822a224d45348dc52779433 192.168.8.134:6706
   slots: (0 slots) master
   replicates e827eafabf2901dcee8bdfbd096427574fced219
M: c4e22dc80492bd0b28830e689de6301a23f4efdb 192.168.8.134:6707
   slots: (0 slots) master
   replicates 77dc0f02db99b74735c5d76aef3a244cfdceef7a
M: 5d1abd29c8902d2c53ecff3d65cb95adc6ad6b25 192.168.8.134:6708
   slots: (0 slots) master
   replicates 56af1ba41b71c86f0e808078cd5ebb4acbe7fa77
[OK] All nodes agree about slots configuration.
>>> Check for open slots...
>>> Check slots coverage...
[OK] All 16384 slots covered.