error when joining cluster

316 views
Skip to first unread message

Pedro Larroy

unread,
Jan 8, 2014, 11:43:43 AM1/8/14
to redi...@googlegroups.com
Hi

I'm trying to join a cluster using revision "90a81b4ebb155c8c07a30f0a0562e7a05fea4294" and get the following error:


piotr@gominola:0:~/storage/devel/redis$ src/redis-trib.rb create localhost:6379 localhost:6380 localhost:6381
>>> Creating cluster
Connecting to node localhost:6379: OK
Connecting to node localhost:6380: OK
Connecting to node localhost:6381: OK
>>> Performing hash slots allocation on 3 nodes...
Using 3 masters:
localhost:6379
localhost:6380
localhost:6381
M: b9f6ad693b3ae5d042b81800a8d797dc1e6bb0a4 localhost:6379
   slots:0-5460 (5461 slots) master
M: f67140ec150e6179afa42648fd2a358f020b8645 localhost:6380
   slots:5461-10921 (5461 slots) master
M: 24a3efea5840527931afd96100d9f590eedf5486 localhost:6381
   slots:10922-16383 (5462 slots) master
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Sending CLUSTER MEET messages to join the cluster
/var/lib/gems/1.9.1/gems/redis-3.0.6/lib/redis/client.rb:85:in `call': ERR Invalid node address specified (Redis::CommandError)
        from /var/lib/gems/1.9.1/gems/redis-3.0.6/lib/redis.rb:2427:in `block in method_missing'
        from /var/lib/gems/1.9.1/gems/redis-3.0.6/lib/redis.rb:36:in `block in synchronize'
        from /usr/lib/ruby/1.9.1/monitor.rb:211:in `mon_synchronize'
        from /var/lib/gems/1.9.1/gems/redis-3.0.6/lib/redis.rb:36:in `synchronize'
        from /var/lib/gems/1.9.1/gems/redis-3.0.6/lib/redis.rb:2426:in `method_missing'
        from src/redis-trib.rb:571:in `block in join_cluster'
        from src/redis-trib.rb:569:in `each'
        from src/redis-trib.rb:569:in `join_cluster'
        from src/redis-trib.rb:781:in `create_cluster_cmd'
        from src/redis-trib.rb:886:in `<main>'





With the following config file:



cat clus.conf | egrep -v '^#' |  grep -v '^$' 
daemonize no
pidfile /var/run/redis.pid
port 6379
timeout 0
tcp-keepalive 0
loglevel notice
logfile ""
databases 16
save 900 1
save 300 10
save 60 10000
stop-writes-on-bgsave-error yes
rdbcompression yes
rdbchecksum yes
dbfilename dump.rdb
dir ./
slave-serve-stale-data yes
slave-read-only yes
repl-disable-tcp-nodelay no
slave-priority 100
appendonly yes
appendfilename "appendonly.aof"
appendfsync everysec
no-appendfsync-on-rewrite no
auto-aof-rewrite-percentage 100
auto-aof-rewrite-min-size 64mb
lua-time-limit 5000
cluster-enabled yes
cluster-config-file nodes-6379.conf
cluster-node-timeout 15000
slowlog-log-slower-than 10000
slowlog-max-len 128
notify-keyspace-events ""
hash-max-ziplist-entries 512
hash-max-ziplist-value 64
list-max-ziplist-entries 512
list-max-ziplist-value 64
set-max-intset-entries 512
zset-max-ziplist-entries 128
zset-max-ziplist-value 64
activerehashing yes
client-output-buffer-limit normal 0 0 0
client-output-buffer-limit slave 256mb 64mb 60
client-output-buffer-limit pubsub 32mb 8mb 60
hz 10
aof-rewrite-incremental-fsync yes



Am I doing something wrong?


Thanks.

Pedro.

Eric Greer

unread,
May 17, 2014, 2:02:29 AM5/17/14
to redi...@googlegroups.com
I have the same exact issue.

[root@redis1 ~]# ./redis-trib.rb create --replicas 1 redis1:6379 redis2:6379 redis3:6379 redis4:6379 redis5:6379 redis6:6379
>>> Creating cluster
Connecting to node redis1:6379: OK
Connecting to node redis2:6379: OK
Connecting to node redis3:6379: OK
Connecting to node redis4:6379: OK
Connecting to node redis5:6379: OK
Connecting to node redis6:6379: OK
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
redis6:6379
redis5:6379
redis4:6379
Adding replica redis3:6379 to redis6:6379
Adding replica redis2:6379 to redis5:6379
Adding replica redis1:6379 to redis4:6379
S: 2cb80d437679f39efb9d2a561663a4f6603a14e0 redis1:6379
   replicates fda3be54c7c0b9b552cd3c360aca80cfd5b557dc
S: d02502eded33a6685964179689e2f4456cc30858 redis2:6379
   replicates a59c46db3989c52296df3f5ff01c3185a41063b7
S: 1756f6f1b64e28b4a6f5f17a7c0c87d9aa37fe66 redis3:6379
   replicates c534713d07485fa76cf47ab470afa52e2d24865d
M: fda3be54c7c0b9b552cd3c360aca80cfd5b557dc redis4:6379
   slots:10923-16383 (5461 slots) master
M: a59c46db3989c52296df3f5ff01c3185a41063b7 redis5:6379
   slots:5461-10922 (5462 slots) master
M: c534713d07485fa76cf47ab470afa52e2d24865d redis6:6379
   slots:0-5460 (5461 slots) master
Can I set the above configuration? (type 'yes' to accept): yes
>>> Nodes configuration updated
>>> Sending CLUSTER MEET messages to join the cluster
/usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis/client.rb:97:in `call': ERR Invalid node address specified (Redis::CommandError)
        from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:2432:in `method_missing'
        from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in `synchronize'
        from /usr/lib/ruby/1.8/monitor.rb:242:in `mon_synchronize'
        from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:37:in `synchronize'
        from /usr/lib/ruby/gems/1.8/gems/redis-3.0.7/lib/redis.rb:2431:in `method_missing'
        from ./redis-trib.rb:621:in `join_cluster'
        from ./redis-trib.rb:619:in `each'
        from ./redis-trib.rb:619:in `join_cluster'
        from ./redis-trib.rb:854:in `create_cluster_cmd'
        from ./redis-trib.rb:1075:in `send'
        from ./redis-trib.rb:1075

Joel de Matos

unread,
Jun 23, 2015, 7:19:51 AM6/23/15
to redi...@googlegroups.com, inte...@gmail.com
Hi, any luck with this?
I'm having a similar problem...

[root@redis-01 ~]# redis-trib.rb create --replicas 1 redis-01:6379, redis-02:6379, redis-03:6379, redis-04:6379, redis-05:6379, redis-06:6379
>>> Creating cluster
Connecting to node redis-01:6379,: OK
Connecting to node redis-02:6379,: OK
Connecting to node redis-03:6379,: OK
Connecting to node redis-04:6379,: OK
Connecting to node redis-05:6379,: OK
Connecting to node redis-06:6379: OK
>>> Performing hash slots allocation on 6 nodes...
Using 3 masters:
redis-01:6379,
redis-02:6379,
redis-03:6379,
Adding replica redis-04:6379, to redis-01:6379,
Adding replica redis-05:6379, to redis-02:6379,
Adding replica redis-06:6379 to redis-03:6379,
M: 14b21bf9601af9276c5bf209ee56693051a38cb6 redis-01:6379,
   slots:0-5460 (5461 slots) master
M: f8f3752a4adcc57c23c8816d3dde0143fce8bfe6 redis-02:6379,
   slots:5461-10922 (5462 slots) master
M: 0e8ed98be67bd8f4062832d671e1901c698d3f0d redis-03:6379,
   slots:10923-16383 (5461 slots) master
S: 88e4ec5c731d9ca5e4ee9e46e23cd11e181979e5 redis-04:6379,
   replicates 14b21bf9601af9276c5bf209ee56693051a38cb6
S: a6b0dfd2eaff344e26b3e1441af16164f57a3526 redis-05:6379,
   replicates f8f3752a4adcc57c23c8816d3dde0143fce8bfe6
S: 36ac35e941846ca19d572d55f139c0303ed12086 redis-06:6379
   replicates 0e8ed98be67bd8f4062832d671e1901c698d3f0d
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
/opt/tigo/apps/ruby/lib/ruby/gems/2.2.0/gems/redis-3.2.1/lib/redis/client.rb:113:in `call': ERR Invalid TCP port specified: 6379, (Redis::CommandError)
        from /opt/tigo/apps/ruby/lib/ruby/gems/2.2.0/gems/redis-3.2.1/lib/redis.rb:2556:in `block in method_missing'
        from /opt/tigo/apps/ruby/lib/ruby/gems/2.2.0/gems/redis-3.2.1/lib/redis.rb:37:in `block in synchronize'
        from /opt/tigo/apps/ruby/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
        from /opt/tigo/apps/ruby/lib/ruby/gems/2.2.0/gems/redis-3.2.1/lib/redis.rb:37:in `synchronize'
        from /opt/tigo/apps/ruby/lib/ruby/gems/2.2.0/gems/redis-3.2.1/lib/redis.rb:2555:in `method_missing'
        from /usr/local/bin/redis-trib.rb:692:in `block in join_cluster'
        from /usr/local/bin/redis-trib.rb:690:in `each'
        from /usr/local/bin/redis-trib.rb:690:in `join_cluster'
        from /usr/local/bin/redis-trib.rb:1002:in `create_cluster_cmd'
        from /usr/local/bin/redis-trib.rb:1373:in `<main>'

Joel de Matos

unread,
Jun 23, 2015, 7:24:18 AM6/23/15
to redi...@googlegroups.com, inte...@gmail.com
got it... problem is with hostname, in my case i had to replace machine names with their ip address, hope this helps


On Saturday, May 17, 2014 at 7:02:29 AM UTC+1, Eric Greer wrote:
Reply all
Reply to author
Forward
0 new messages