MOVED: MOVED slot ip:port (cluster redirect)
RedisWhat does it mean?
In Redis Cluster, the hash slot holding the requested key belongs to another node. The server permanently redirects the client to the correct node. This is a redirect rather than an error.
Why does it happen?
A client that is not cluster-aware sends a request to the wrong node, slots have been redistributed between nodes (resharding), or the slot map cached by the client is stale.
How to fix it
Use a cluster-aware client library; these follow the MOVED reply automatically, redirect to the correct node and update the slot map. Use the -c flag when connecting with redis-cli. Make sure your client refreshes the slot topology periodically (CLUSTER SLOTS/SHARDS).
More from this engine
- BUSYBUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE
- MISCONFMISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk
- CROSSSLOTCROSSSLOT Keys in request don't hash to the same slot
- ASKASK slot ip:port (cluster redirect)
- NOSCRIPTNOSCRIPT No matching script. Please use EVAL
- EXECABORTEXECABORT Transaction discarded because of previous errors
- NOPERMNOPERM this user has no permissions to run the command or access one of the keys