redis-py Add support for missing command LATENCY RESET (Fix)

The Fix

Adds support for the LATENCY RESET command in the Redis client, allowing users to reset latency spikes time series for events.

Based on closed redis/redis-py issue #1982 · PR/commit linked

Production note: Watch p95/p99 latency and retry volume; timeouts can turn into retry storms and duplicate side-effects.

Open PR/Commit

@@ -265,6 +265,9 @@ class AbstractRedisCluster:
                 "TIME",
                 "GRAPH.CONFIG",
+                "LATENCY HISTORY",
+                "LATENCY LATEST",
+                "LATENCY RESET",

fix.md

Option A — Apply the official fix\nAdds support for the LATENCY RESET command in the Redis client, allowing users to reset latency spikes time series for events.\nWhen NOT to use: This fix should not be used if the LATENCY RESET command is not supported by the Redis server version.\n\n

Why This Fix Works in Production

Trigger: Add support for missing command LATENCY RESET
Mechanism: The Redis client lacked support for the LATENCY RESET command, preventing users from resetting latency spikes

Production impact:

If left unfixed, tail latency can spike under load and surface as timeouts/retries (amplifying incident impact).

Why This Breaks in Prod

The Redis client lacked support for the LATENCY RESET command, preventing users from resetting latency spikes
Production symptom (often without a traceback): Add support for missing command LATENCY RESET

Proof / Evidence

GitHub issue: #1982
Fix PR: https://github.com/redis/redis-py/pull/2503
Reproduced locally: No (not executed)
Last verified: 2026-02-12
Confidence: 0.80
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.82

Discussion

High-signal excerpts from the issue thread (symptoms, repros, edge-cases).

Jump to Sources Open on GitHub

Failure Signature (Search String)

Add support for missing command LATENCY RESET

Copy-friendly signature

signature.txt

Failure Signature
-----------------
Add support for missing command LATENCY RESET

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
Add support for missing command LATENCY RESET

What Broke

Users were unable to reset latency spikes, affecting performance monitoring.

Why It Broke

The Redis client lacked support for the LATENCY RESET command, preventing users from resetting latency spikes

Fix Options (Details)

Option A — Apply the official fix

Adds support for the LATENCY RESET command in the Redis client, allowing users to reset latency spikes time series for events.

When NOT to use: This fix should not be used if the LATENCY RESET command is not supported by the Redis server version.

Fix reference: https://github.com/redis/redis-py/pull/2503

Last verified: 2026-02-12. Validate in your environment.

When NOT to Use This Fix

This fix should not be used if the LATENCY RESET command is not supported by the Redis server version.

Did This Fix Work in Your Case?

Quick signal helps us prioritize which fixes to verify and improve.

Prevention

Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
Pin production dependencies and upgrade only with a reproducible test that hits the failing path.

Related Issues

No related fixes found.

Cluster: redis-py:latency redis-py hub redis-py best practices All hubs All clusters

Related clusters: Configuration error Retry storm Data consistency

Sources

We don’t republish the full GitHub discussion text. Use the links above for context.