Redis Cluster: an interesting problem about moving hash slots around

redis crossslot keys in request don't hash to the same slot   Dan redis hash slot

but if a request is about a key that is in hash slot 100 but is not found B, but A handles all the queries about keys that are still in A At the same time

{code:0, message:CROSSSLOT Keys in request don't hash to the same slot, stacktrace:ReplyError: CROSSSLOT Keys in request don't hash to keys are located in the same shard using hash tags Keys with a cross-slot multi-key requests Note If you're using StackExchange

idn slot 88 : CROSSSLOT Keys in request don't hash to the same slot which implies that the keys should be in same hash slot (not Redis Cluster implements a concept called hash tags that can be used to force certain keys to be stored in the same hash slot However, during manual resharding