redis-clustering

Redis Clustering Guidance for designing keys and routing reads in a sharded Redis Cluster (and in standalone primary/replica replication). Covers the two failure modes that bite most new cluster users: CROSSSLOT errors on multi-key operations, and overloading primaries with read traffic. When to apply Designing keys for a Redis Cluster deployment. Debugging a CROSSSLOT error on MGET , SDIFF , transactions, or pipelines. Implementing transactions / Lua scripts that touch multiple keys. Scaling out read traffic without adding shards. 1. Hash tags for multi-key operations Redis Cluster distributes keys across 16,384 slots by hashing the key name. Any command that touches multiple keys ( MGET , SDIFF , SUNIONSTORE , transactions, pipelines, Lua scripts with multiple KEYS[] ) requires all keys to live on the same slot — otherwise the server returns a CROSSSLOT error. Hash tags force this: the part between { and } is the only thing hashed for slot assignment, so two keys sharing a hash tag always land together. Show more Installs 830 Repository redis/agent-skills GitHub Stars 92 First Seen May 26, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass