ERDOWN redis cluster_error ai_generated partial

CLUSTERDOWN The cluster is down

ID: redis/clusterdown

Also available as: JSON · Markdown
65%Fix Rate
85%Confidence
3Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
7 active — — —

Root Cause

Redis Cluster has lost quorum or has uncovered hash slots. One or more master nodes are down without a failover replica.

generic

Workarounds

  1. 90% success Check cluster status and identify failed nodes 
    redis-cli --cluster check 127.0.0.1:7000

    Sources: https://redis.io/docs/

  2. 85% success Fix or replace the failed node and let cluster recover 
    redis-cli --cluster fix 127.0.0.1:7000  # reassigns orphaned slots
  3. 78% success Add replicas to prevent future CLUSTERDOWN 
    redis-cli --cluster add-node new_node:7006 existing:7000 --cluster-slave

Dead Ends

Common approaches that don't work:

  1. Force a failover on all nodes 82% fail

    Forcing failover on healthy nodes can cause split-brain and data loss

  2. Restart all cluster nodes simultaneously 78% fail

    Simultaneous restart loses cluster state; nodes may not rejoin properly