Redis runs commands on one main thread and keeps your data in memory, so peak traffic finds both limits. Set maxmemory and an eviction policy first, then track latency and plan failover. Start with Fix Redis OOM with maxmemory and an Eviction Policy.
- Find Redis High Latency, Slow Commands and Hot Keys
Alert on per-command p99, slow log growth and a busy main thread, then trace Redis hot keys and big keys, so p99 spikes get a cause before users notice.
- Redis Sentinel Failover Without Lost or Refused Writes
Run three Sentinels and make clients ask Sentinel for the primary, so writes stop failing with READONLY You can't write against a read only replica.
- Fix Redis OOM with maxmemory and an Eviction Policy
Cap Redis with maxmemory below its container limit and match the eviction policy to its role, so peak traffic evicts keys or refuses writes without a crash.