CLUSTERDOWN: CLUSTERDOWN The cluster is down / Hash slot not served
RedisWhat does it mean?
Redis Cluster is not fully operational. Some hash slots are not served by any node, so the cluster rejects requests.
Why does it happen?
Not enough master nodes reachable, one or more slots unassigned/uncovered, loss of majority (quorum), node crashes, or some slots unreachable while cluster-require-full-coverage is yes.
How to fix it
Check cluster state: CLUSTER INFO and CLUSTER NODES. Bring down masters back up, or let replicas be promoted. Reassign unassigned slots (redis-cli --cluster fix or CLUSTER ADDSLOTS). Verify that all slots are covered. If partial operation is acceptable, consider cluster-require-full-coverage no.
More from this engine
- WRONGPASSWRONGPASS invalid username-password pair or user is disabled
- READONLYREADONLY You can't write against a read only replica
- MASTERDOWNMASTERDOWN Link with MASTER is down and replica-serve-stale-data is set to 'no'
- LOADINGLOADING Redis is loading the dataset in memory
- 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