CLUSTER COUNTKEYSINSLOT Docs

slot Multi-key operations executed on a Redis cluster cannot work if keys belong to different hash slots But, you

Redis Cluster The information present is - slot ranges, host, port and few metrics gathered from redis INFO Command Master-Replica Layout

redisexceptionsresponseerror_ crossslot keys in request don''t hash to the same slot Redis sharding is a method of splitting the keyspace into 16384 hash slots for distribution across nodes It enhances scalability and manages traffic surges,

redis hash slot Here, owner-id is the node id of the instance where the hash slot has been moved This command should only be run for master nodes $ redis