Channels - Unable to use redis as sharded cluster

Error: crossslot keys in request don't hash to the same slot redis exceptions responseerror_ crossslot keys in request don't hash to the same slot 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 oyo 88 slot : CROSSSLOT Keys in request don't hash to the same slot which implies that the keys should be in same hash slot (not

agen gacor slot login requests in a row For instance if the RTT time is 250