Keys in different slots
A multi-key command that fails with CROSSSLOT once sharded
MGET user:1:name user:2:email
Redis Cluster Compatibility Checker
Paste commands, one per line. Everything here works on a single instance. The point is what stops working the day the data is sharded, which is usually long after the code was written and always at the worst moment.
Paste below, or drop a file anywhere on this panel
Or drop a file anywhere on this panel. Nothing is uploaded: the analysis runs in this tab.
The answer appears here
Paste on the left and press Check. Nothing leaves this tab.
Formatted
Results
Nothing else to flag.
No formatting problems, and nothing the rules object to. Worth remembering what that covers: this reads the file you pasted, not the account or cluster it will be applied to.
No finding matches that filter.
Examples
Real input you can load into the tool above. Each one shows a different thing going wrong, because that is what the tool is for.
The same command, hash-tagged
The keys share a slot, so this one works on a cluster
MGET user:{42}:name user:{42}:emailCommon mistakes
These are the ones that fail silently. The config is accepted, nothing raises an error, and the consequence arrives later.
Assuming a multi-key command works because it works today
On a single instance every key is in the same place. The failure appears only after sharding.
Instead:Hash-tag keys that are read together.
Keeping a database index in the connection string
Cluster mode has only database 0 and SELECT fails on anything else.
Instead:Remove the index and use key prefixes.
Running KEYS or DBSIZE against one node for a cluster-wide answer
Each node knows only its own slots, so the answer is a fraction.
Instead:Query every primary and combine.
Building key names inside a Lua script
Routing uses the declared KEYS. A key built in the body is invisible to it.
Instead:Pass every key through KEYS.
What cluster mode takes away
Cluster mode is not a transparent scale-out. Several things that worked before stop working, and they fail in ways that point at your application rather than at the cluster.
Multi-key commands need every key in one slot
MGET, MSET, SUNION, ZUNIONSTORE, RENAME and the rest fail with CROSSSLOT unless the keys share a slot. This works on a single instance, and on a cluster where the keys happen to collide, so it can pass every test you have and fail in production. A shared hash tag is what makes it reliable.
Only database 0 exists
SELECT on any other index fails. A connection URL carrying a database number cannot work at all, and the error surfaces at connect time rather than where the number was configured.
KEYS, SCAN, DBSIZE and FLUSHDB answer for one node
Each node knows only its own slots. Code that runs one of these against a single node and treats the answer as the keyspace silently sees a fraction of it, and the fraction changes as slots move.
Transactions and scripts are bound by the same rule
Every key touched between MULTI and EXEC must share a slot, and the failure arrives at EXEC rather than at the command that introduced the second slot. A Lua script is routed by its declared KEYS, so a key built inside the script body is invisible to routing and the script runs on a node that may not own it.
Pub/sub is broadcast unless it is sharded
An ordinary PUBLISH propagates across the whole cluster bus, so it reaches every subscriber on every node. That is convenient and it means pub/sub throughput does not improve as you add shards. SPUBLISH and SSUBSCRIBE, added in Redis 7.0, are routed by slot instead.
Related redis tools
Redis Hash Tag Tester Will these keys survive a multi-key command? Redis Hash Slot Calculator Which of the 16,384 slots does this key land in? Redis CLUSTER NODES Parser Read the topology, and find the gap Redis Cluster Slot Distribution Who owns how much, and what is missing Redis Cluster Sizing Only 60% of each node is usable Redis Cluster Config Generator Three primaries, and the bus port open
All 53 redis tools