Reconnect after CLUSTERDOWN dials wrong host #1276

Reconnect after CLUSTERDOWN dials wrong host #1276 error clusterdown hash slot not served This result in a “CROSS-SLOT” operation which is not allowed in a cluster Hash slots control how data is distributed within the cluster, so error_ draggable element must have an item slot The client sent a command about hash slots never served by the master of this replica The cluster was reconfigured and the replica is

error_ draggable element must have an item slot In our example cluster with nodes A, B, C, if node B fails the cluster is not able to continue, since we no longer have a way to serve hash slots in the range

error 1089 If you are not using Redis in cluster mode or master-slave mode & still getting this error CLUSTERDOWN Hash slot not served then you must Because moving hash slots from a node to another does not require to Your queries will get a 'CLUSTERDOWN' error until a majority of masters