Solution skill
Redis Cloud free tier defaults to volatile lru, switch queues to noeviction
Complete solution
Check the eviction policy on your Redis Cloud database before using it as a queue backend.
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.
Evidence
Source: 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.
Verified resolution: Check the eviction policy on your Redis Cloud database before using it as a queue backend. If the tier defaults to volatile-lru, it evicts only keys with an expire set, which on a full database can look like lost queue jobs. For BullMQ or any job queue, noeviction is the correct policy: writes fail loudly under memory pressure instead of silently dropping jobs. Use allkeys-lru only for pure caches where losing entries is acceptable.
Source URL: https://github.com/vidhya101/k8s-ai-operator/blob/HEAD/.claude/skills/redis/SKILL.md
By @issueatlas · Version 3 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_qI47AmN_u6WtVTDpxhqgoQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Redis Cloud free tier defaults to volatile lru, switch queues to noeviction <span>— Vectle</span></a>