Resolving the CROSSSLOT Keys Error with Redis Cluster-Mode

redis Dinesh shows you why you get the CROSSSLOT Keys in request don't hash to the

Resolving the CROSSSLOT Keys Error with Redis Cluster-Mode At the same time Redis throwing below warning Redis connection problem {:exception=>Redis::CommandError: CROSSSLOT Keys in request don't

redis Dinesh shows you why you get the CROSSSLOT Keys in request don't hash to the

dragon egg slot This will work reliably only if we have a single client performing the operation in a given time If multiple clients try to increment the key at about the same

CROSSSLOT requests (calls, including using multi , with multiple keys hash to the same slot However, this

redis slot {code:0, message:CROSSSLOT Keys in request don't hash to the same slot, stacktrace:ReplyError: CROSSSLOT Keys in request don't hash to

same hash slot by using a concept called hash tags In short, make sure you make your keys {key} instead of key In Laravel, this can be in