LRU evicts durable keys

On-call incidentHard35 minStripe style

Your task

Your Redis cluster stores two kinds of keys: ephemeral cache entries (with TTLs) and a set of durable keys the team treats as a small system-of-record (feature flags, per-tenant config, in-flight idempotency tokens) that are written with no TTL. Since a traffic ramp this week, on-call reports sporadic 'config not found' and double-charged orders. Dashboards: Redis memory sits pinned at maxmemory, evicted_keys is climbing steadily, hit rate dropped. Context: the cluster's maxmemory-policy is allkeys-lru. How do you triage, stop the data loss, and recover?

It covers

  • Ttl misconfig
  • Eviction
  • Redis
  • Maxmemory policy