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

redis CROSSSLOT Keys in request don't hash to the same slot redis crossslot keys in request don't hash to the same slot but if a request is about a key that is in hash slot 100 but is not found B, but A handles all the queries about keys that are still in A At the same time redisexceptionsresponseerror_ crossslot keys in request don''t hash to the same slot GeminiDB Redis执行多Key命令时，可能会出现“CROSSSLOT Keys in request don't hash to the same slot”报错。Redis集群架构不支持跨Slot执行涉及多Key的命令，

redisexceptionsresponseerror_ crossslot keys in request don''t hash to the same slot Why CROSSSLOT Keys in request don't hash to the same slot error happens in a Redis Cluster, and how to solve it

redis crossslot keys in request don''t hash to the same slot T12:03: ReplyError: CROSSSLOT Keys in request don't hash to the same slot T12:03: at parseError (appnode_modules CROSSSLOT Keys in request don't hash to the same slot ERR READONLY you can't No way to dispatch this command to Redis Cluster because keys have different