Redis: TLS Cluster Ports Get Module Visibility
Three related pull requests give modules a reliable way to see and react to TLS cluster port selection, while a separate fix stabilizes a flaky replication buffer test in daily CI.
Duration: PT2M17S
Episode overview
This episode is a short developer briefing from Redis.
It explains recent repository work in plain language.
- Show: Redis
- Published: 2026-07-23T13:13:16Z
- Audio duration: PT2M17S
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 July 23rd, and here's your Redis briefing.
Today's biggest thread is about giving modules better visibility into TLS cluster configuration. Three pull requests build on each other here. PR 15517, from GuyAv46, adds a new flag so modules can tell whether the port returned by "get cluster node info" is actually the TLS port. That closes a gap where modules had…
Separately, PR 15516 from TalBarYakar is a broader bootstrap enhancement, adding list and dry-run arguments to the module bootstrap process. It's still in review with substantial discussion, eighteen comments so far, so expect more iteration before it lands.
On the reliability side, minchopaskal's PR 15503, and the matching commit a4fa36e, fixed a daily CI failure in the replication buffer tests. The root issue was a test incorrectly enabling dual channel RDB replication for compression scenarios where it should have stayed off, plus a miscount of partial…
What to watch next: keep an eye on PR 15516 as it works through review, and expect the replication buffer test's root cause to surface as a follow-up once someone digs into why PSYNC rejection isn't behaving as expected.
That's the briefing for July 23rd. Back…
Nearby episodes from Redis
- Waking Sleepers and Closing Edge Cases
- Protocol Correctness and Replication Memory Accounting
- Replication Compression Lands, Durability Bugs Squashed
- Weekly Recap - Replication, Persistence, and Memory Efficiency
- Build Environment Cleanup
- Storage Overhauls and a Security Patch
- Correctness Fixes and a Module Refresh
- Correctness Under Concurrency