Redis: Memory Tracking Configuration Fix

Transcript

Good morning, this is your Redis development update for May 16th, 2026.

Mincho Paskalev merged pull request #15005, which adds proper error handling for enabling memory tracking in non-clustered mode. The issue was that Redis was incorrectly validating runtime changes to memory tracking settings when not running in cluster mode. Previously, the checks were allowing operations that should have been forbidden.

The fix involved a single boolean condition change in the `updateMemoryTrackingEnabled()` function within `src/config.c`. When memory tracking is disabled and administrators attempt to enable it at runtime using the `cluster-slot-stats-enabled mem/yes` command, Redis will now properly reject the operation in non-clustered environments, matching the intended behavior.

The pull request also updated the corresponding test suite in `tests/unit/cluster/slot-stats.tcl` to verify this stricter validation works correctly. The changes were reviewed and approved, with four comments addressing implementation details.

This is classified as a low-risk change since it only affects a specific configuration scenario and adds stricter validation rather than loosening existing controls.

What's next: This fix improves configuration consistency across different Redis deployment modes and prevents potential runtime issues from incorrect memory tracking states.

That's your Redis update. I'm back tomorrow with more development news.