Redis: Sentinel CPU Fix and Failover Safety
Sentinel's 100% CPU busy-loop fix merged alongside open proposals to prevent split-brain failover, plus faster RDB and AOF loading. The day's pattern is reliability under network failure, backed by a broad sweep of silent-corruption and accounting fixes.
Duration: PT2M37S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-09-23T13:17:00Z
- Audio duration: PT2M37S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's September 23rd, 2026 — this is your Redis briefing.
Lead: The big signal today is reliability when connections fail, with a merged fix for Sentinel burning CPU and a set of open proposals to stop failover from splitting the cluster.
First, high availability. PR 15107, merged yesterday, fixes Sentinel spinning at 100 percent CPU after a monitored instance becomes unreachable, common after Kubernetes pod IP rotation. The root cause was an unconsumed async socket error that kept waking the event loop, and the fix checks and clears that pending…
Second, a broad correctness sweep, mostly from one contributor, targeting silent corruption and accounting drift. Examples include PR 15847 fixing a byte-count overflow when moving the tail of very large intsets, PR 15845 fixing saturated bit-field sets clamping to the wrong bound, plus fixes for dict rehash stalls…
Finally, performance and hygiene. Commit 7a72677, from PR 15782, hints sequential access when loading R D B and A O F files, cutting load times by roughly 12 to 26 percent on network storage by widening kernel read-ahead. Two version PRs restore the unstable branch marker and set the 8.12 milestone version.
What's…
Nearby episodes from Redis
- Shutdown Safety, Migration Visibility, and Faster Bit Operations
- Stream Trim Corruption Fix and Migration Test Isolation
- Weekly Recap - Security Releases and Memory Control
- Stream Trim Persistence Risk and Cleaner Scans
- Scan Command Cleanup
- Security Patches Ship Across Five Release Lines
- Data Correctness Fixes Across Streams, Sorted Sets, and Scripting
- Security Patches Roll Backward Across Four Release Lines