Reconnect after CLUSTERDOWN dials wrong host #1276

CLUSTERDOWN Hash slot not served Once the cluster was fully reconfigured, we then had some services stuck on these errors : dial

The client sent a command about hash slots never served by the master of this replica The cluster was reconfigured and the replica is

keraton bet slot 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

star 777 slot login 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