antirez/redis — Issue #164: wrong get using cluster makes cluster unavailable
Author: davos1
Created: 2011-10-27 04:47:52+00:00
State: open

Hi, it seems that calling a wrong command makes cluster unavailable:

redis 127.0.0.1:6379> SORT mli BY weight_* Store resultkey
(integer) 6

now an error causes cluster unavailable:

rredis 127.0.0.1:6379> get resultkey
(error) ERR Operation against a key holding the wrong kind of value
redis 127.0.0.1:6379> mget resultkey
1) (nil)
redis 127.0.0.1:6379> mget resultkey 0 -1
(error) ERR Multi keys request invalid in cluster
redis 127.0.0.1:6379> mget resultkey 0 (
Could not connect to Redis at 127.0.0.1:6379: Connection refused
(1.04s)
not connected> mget resultkey 0 (
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> get resultkey
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> get resultkey
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> connect 127.0.0.1 6379
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> cluster info
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> get foo
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> connect 127.0.0.1 6379
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> cluster nodes
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> exit
customer-187-174-213-84:src alberto$ redis-cli
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> connect 127.0.0.1 6379
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> ping
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected>