redis集群报错CROSSSLOT Keys in request don't hash to the same

error crossslot keys in request don't hash to the same slot   Dan error_ replication slot is active for pid

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

CROSSSLOT Keys in request don't hash to the same slot Solution 1 One solution is to force redis to insert the keys into same slot We can achieve CROSSSLOT Keys in request don't hash to the same slot · Before you run a command that involves multiple keys, use the CLUSTER KEYSLOT command to

vip slot club casino : CROSSSLOT Keys in request don't hash to the same slot which implies that the keys should be in same hash slot (not {code:0, message:CROSSSLOT Keys in request don't hash to the same slot, stacktrace:ReplyError: CROSSSLOT Keys in request don't hash to