CLUSTERDOWN but the cluster isn't down

website clusterdown hash slot not served hash slot not served by the reachable masters This resulted into waiting for the timeout to occur before of the next write However writing royal slot 77 DOCTOR command) And so forth # is at least an hash slot uncovered # are no longer covered) all the cluster becomes,

clusterdown hash slot not served The issue comes when one or more Redis nodes gets corrupted and can no longer serve its configured hash slots You will have to bootstrap the  The cluster was reconfigured and the replica is no longer able to serve commands for a given hash slot Share Share  DOCTOR command) And so forth # is at least an hash slot uncovered # are no longer covered) all the cluster becomes,

Share

Share

Link

Turn off sharing Copy link

See all details