CLUSTERDOWN: hash slot not served response from node not part of cluster

[shailymittal]

I ran memtier benchmark on a redis cluster
Some details about the benchmark

1. Commands - set:get commands
2. Key types - string
3. Wait commands - no

During the benchmark, one of the Master node in the cluster failed over and was removed from the cluster and I started getting below error
-CLUSTERDOWN: hash slot not served
error from the cluster even though at the time this node was not part of not cluster for every "CLUSTER INFO" command was returning "I am no longer part of any cluster"

@YaacovHazan : could you help with this?

[YaacovHazan]

Hi @shailymittal . IIUC, once one of the Master nodes failed over and was removed from the Cluster, you lost full slot range coverage and started getting the -CLUSTERDOWN: hash slot not served

A few Q's:

1. From where did you get the I am no longer part of any cluster error? It isn't a Redis response (at least not the OSS Redis).
2. Why are you asking about blocking command? How blocking command related to the issue?

[shailymittal]

1. This is our custom response for CLUSTER INFO when node is not in cluster (not OSS redis).
2. My bad about the blocking command. One of the reason, REDIS can send this response is when client is blocked and then slot is not served so I was wondering if memtier is sending some blocking command.

Also, should we handle -CLUSTERDOWN: kind of error assuming if some node has incorrect info of the slots and have a topology refresh in this case?