Redis: Cluster Bus Security and a Flaky Test Fix
One pull request tightens security around the cluster bus by making unencrypted traffic an explicit opt-in rather than a silent default, while a second fixes a timing race in the active-expire test suite that was causing intermittent CI failures under Valgrind.
Duration: PT2M10S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-08-29T13:12:53Z
- Audio duration: PT2M10S
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 August 29th, 2026, and this is your Redis briefing.
Today's activity centers on two very different but equally important concerns: production security posture, and test suite reliability.
Let's start with the bigger one. PR 15722, from Hristo Staykov, addresses a real gap in how the Redis cluster bus handles trust. Right now, nodes identify each other using a node ID carried in the packet header — but that ID is public information. Anyone who can reach the bus port can speak the protocol. And by…
Second theme: test reliability. PR 15723, from Vitali Hlinski, targets a race condition in the active-expire test. The test sets a key with a fifty-millisecond expiry, then calls a reset function — but under Valgrind's slower execution, the cron job can expire that key and fire its post-notification job in the gap…
What's next: expect the cluster bus change to prompt a look at TLS settings in existing deployments, and expect the expire-test fix to stabilize the daily CI signal, so future red builds are more likely to reflect real regressions rather than timing noise.
That's the briefing for today. Stay secure, stay tested.
Nearby episodes from Redis
- Quietly Failing Configs Get a Voice
- Chasing Timing Bugs Across the Stack
- Shoring Up CI and Config Safety
- Correctness Fixes and a Fast Clock Rollout
- Correctness Fixes and Command-Line Hardening
- Weekly Recap - A Coordinated Security Push Across Every Supported Line
- Correctness Bugs Sweep Across Core Commands
- TLS Hardening Takes Center Stage