crossslot keys in request don't hash to the same slot ✓ CROSSSLOT Error when using external Redis Cluster (AWS

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

Change key names and use hash tags to ensure that the involved keys are in the same slot Avoid data skew when you use hash tags For more

shows you why you get the CROSSSLOT Keys in request don't hash to the same slot

ERR CROSSSLOT Keys in request don't hash to the same slot within 'MULTI' > EXPIRE user

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

ResponseError: CROSSSLOT Keys in request don't hash to the same slot which implies that the keys should be in same hash slot (not just in same