Redis: Trust Boundaries Get Tighter
Today's merges focus on closing gaps where Redis silently trusted things it shouldn't have—unauthenticated cluster bus ports, passwordless users, and dropped RESP3 sessions—while a new BLESS command and an AOF timing estimate expand operational control over memory and recovery.
Duration: PT2M38S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-09-15T13:13:36Z
- Audio duration: PT2M38S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, it's September 15th, and here's your Redis briefing.
The clear pattern across today's activity is Redis tightening trust boundaries that used to rely on operators getting configuration right by accident.
Start with PR 15722, from Hristo Staykov. It introduces a new setting, cluster bus port protected mode, on by default. Until now, a cluster node's bus port had no authentication of its own—only TLS cluster provided that, and it's off by default. This change means a cluster node now refuses to start unless its bus is…
That same theme—don't let weak defaults create silent risk—shows up in two open PRs. PR 15793 from vitahlin fixes redis-cli so that supplying a username without a password actually authenticates against that user, instead of quietly falling back to the default user. And PR 15796 from Stav Levi addresses RESP-3…
On the feature side, two larger merges. PR 15649 adds BLESS, a new command family for marking keys as non-evictable under maxmemory—protection that persists through restarts, replication, and slot migration, with a deliberate overshoot allowance so a heavily-blessed keyspace doesn't lock up entirely. And PR 15665…
What to remember: if you run clusters…
Nearby episodes from Redis
- Checksum Performance and a Version Bump Cluster
- Weekly Recap - Correctness Fixes and Read-Path Performance
- Hardening Under Concurrency
- Hardening Persistence and Trimming Clock Overhead
- Shaving Branch Misses Out of SipHash
- Correctness Fixes in Replication and Diagnostics
- Correctness Fixes and Core Refactors Converge
- Correctness Fixes Meet CPU-Level Performance Tuning