Skip to product information
1 of 1

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

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

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

Regular price 1000 ₹ INR
Regular price Sale price 1000 ₹ INR
sell Sold out

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

website replyerror_ crossslot keys in request don't hash to the same slot When multi-key commands are executed in a GeminiDB Redis instance, the error CROSSSLOT Keys in request don't hash to the same slot may be bo99 slot I am getting this error as well: Error writing from RESTDataSource to cache: ReplyError: CROSSSLOT Keys in request don't hash to the same slot

replyerror_ crossslot keys in request don't hash to the same slot This error message indicates that some of the keys in your request are mapped to different hash slots, which is preventing the operation from being executed   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  In a cluster topology, the keyspace is divided into hash slots Different nodes will hold a subset of hash slots Multiple keys operations

See all details