Scaling a High-traffic Rate Limiting Stack with Redis Cluster

CLUSTER SETSLOT Docs redis 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 redis hash slot Redis Cluster partitions its data across 16,384 slots, each assigned to a specific node The primary reason for resharding is to recalibrate

redis crossslot keys in request don''t hash to the same slot CLUSTER GETKEYSINSLOT slot count Available since 0 The command returns an array of keys names stored in the contacted node and hashing to the specified