ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #redis
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Reducing operational costs for low-traffic workloads often involves transitioning from persistent servers to serverless architectures. While FeathersJS supports this decoupling, the stateless nature of serverless functions creates a conflict with the framework's real-time capabilities. In a standard deployment, Socket.io manages persistent connections to bro
Goal: Configure Redis to return the current (stale) value of an expired key while a background process refreshes it, providing a stale‑while‑revalidate behavior without requiring application‑level logic. Constraints: Redis presently returns nil for expired keys; the lazyfree‑lazy‑expire setting only changes when the key is removed from memory, not what is se
Moodle's documented session handling supports several backends, including the default database handler and optional Redis and Memcached handlers configured under Site administration > Server > Session handling. The documentation also describes an exclusive per-session lock that Moodle takes while serving a request, intended to prevent race conditions w
Goal: achieve the lowest possible write latency in Redis while maintaining a durability level that tolerates at most a few seconds of data loss. Understanding the trade‑off is complicated because the latency impact of RDB, AOF, and the hybrid mode varies with the fsync policy (always, everysec, no) and with how often background rewrites are triggered. Which
Diagnosing Intermittent Connection Pool Exhaustion In a highly‑available ArgoCD cluster, sync waves and frequent repository polling can trigger “pool exhausted” or “dial tcp” errors. The root cause is the mismatch between the per‑pod connection pools ArgoCD maintains for Redis and PostgreSQL and the hard limits those backends enforce. ArgoCD exposes two docu
Redis Cluster upgrade failure recovery decision During a rolling upgrade, a node that fails after accepting writes but before completing the upgrade can leave Redis Cluster in a mixed-version state: a master may have lost its slots while a replica runs a different binary. Redis does not support downgrades, and RDB or AOF files rewritten by the newer version
Implementing a least-privilege security model in Redis 7.0+ requires granular Access Control Lists (ACLs) to restrict users to specific keyspaces and command categories. A primary challenge arises when managing the lifecycle of these credentials, specifically when rotating passwords or updating permissions to prevent credential staleness. There are two prima
Consistency Goals in Redis OSS Clusters When utilizing Amazon ElastiCache for Redis with read replicas, the primary goal is to scale read throughput while maintaining acceptable data freshness. Because replication from the primary node to replicas is asynchronous, there is an inherent risk of stale reads where a client retrieves an older version of a key imm
argocd