ReplyError: CROSSSLOT Keys in request don't hash to the same slot

ReplyError: CROSSSLOT Keys in request don't hash to the same slot error crossslot keys in request don't hash to the same slot CROSSSLOT Keys in request don't hash to the same slot This is where the concept of hash tags comes in Hash tags allow us to force error_ replication slot is active for pid I am getting this error as well: Error writing from RESTDataSource to cache: ReplyError: CROSSSLOT Keys in request don't hash to the same slot

error_ replication slot is active for pid So if I know the key I can delete it by the following command without problem: CROSSSLOT Keys in request don't hash to the same slot

error_ draggable element must have an item slot error: ERR CROSSSLOT Keys in request don't hash to the same slot I'm not doing this redis · fudu's user avatar · fudu 694 answered May 2 at 9:09 3 votes  : CROSSSLOT Keys in request don't hash to the same slot which implies that the keys should be in same hash slot (not