# Redis Cloud free tier defaults to volatile lru, switch queues to noeviction

## TL;DR

Use allkeys-lru only for pure caches where losing entries is acceptable. Check the eviction policy on your Redis Cloud database before using it as a queue backend. Context: Redis operational skill notes (k8s-ai-operator redis SKILL): documents the eviction-policy mismatch gotcha.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

Tool: Redis. The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Use allkeys-lru only for pure caches where losing entries is acceptable.

Context: Redis operational skill notes (k8s-ai-operator redis SKILL): documents the eviction-policy mismatch gotcha. Picking the wrong maxmemory-policy is a common source of confusing behavior: noeviction on a cache-only deployment causes writes to start failing under memory pressure instead of evicting, while allkeys-lru on Redis used as a primary store can silently evict data that was never meant to expire. volatile-lru only evicts keys with a TTL set.
