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

Error: crossslot keys in request don't hash to the same slot error crossslot keys in request don't hash to the same slot The fix here is to use hash tags for data that always needs to be in the same slot See topicscluster-spec#:~:text=Hash% error 1089 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 1089 When an operation requires multiple keys, all the involved keys must map to the same hash slot for the operation to be executed atomically and consistently

error_ draggable element must have an item slot Connect to your Redis Cluster: Create two new keys and checkout their assigned hash-slot: redis> SET mykey1 Hello redis> SET mykey2 Hello 2 redis集群报错CROSSSLOT Keys in request don't hash to the same slot，先上结果：$redis->sDiffStore('live_room:robots:data:'