What Do I Do If Error " CROSSLOT Keys in request don't hash to the same slot" Is Displayed?

Scenarios

When multi-key commands are executed in a GeminiDB Redis instance, "CROSSLOT Keys in request don't hash to the same slot" may be reported.

Possible Causes

Commands involving multiple keys were executed across slots in a GeminiDB Redis cluster instance. For example, EVAL and BRPOPLPUSH were executed across slots.

Solution

• Change key names and use hashtags to ensure that the keys are in the same slot. Avoid data skew when you use hashtags. For more information, see Which Commands Require Hashtags on GeminiDB Redis Cluster Instances?
• When hashtags cannot be used, change the instance type to primary/standby. For details, see Compatible API and Versions.