redis-py Add support for LATENCY HISTOGRAM (Fix)

The Fix

pip install redis==7.1.0

Based on closed redis/redis-py issue #2124 · 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

@@ -1044,6 +1044,15 @@ def memory_purge(self, **kwargs) -> ResponseT:
         return self.execute_command("MEMORY PURGE", **kwargs)
 
+    def latency_histogram(self, *args):
+        """
+        This function throws a NotImplementedError since it is intentionally

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: Do not use this fix if LATENCY HISTOGRAM support is required.\n\n

Why This Fix Works in Production

Trigger: No direct production impact, but functionality is intentionally not supported.
Mechanism: Implemented LATENCY HISTOGRAM by throwing NotImplementedError in the client
Why the fix works: Implemented LATENCY HISTOGRAM by throwing NotImplementedError, addressing issue #2124. (first fixed release: 7.1.0).

Production impact:

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

Why This Breaks in Prod

Implemented LATENCY HISTOGRAM by throwing NotImplementedError in the client
Production symptom (often without a traceback): No direct production impact, but functionality is intentionally not supported.

Proof / Evidence

GitHub issue: #2124
Fix PR: https://github.com/redis/redis-py/pull/2147
First fixed release: 7.1.0
Reproduced locally: No (not executed)
Last verified: 2026-02-09
Confidence: 0.95
Did this fix it?: Yes (upstream fix exists)
Own content ratio: 0.72

Discussion

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

Jump to Sources Open on GitHub

Failure Signature (Search String)

No direct production impact, but functionality is intentionally not supported.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
No direct production impact, but functionality is intentionally not supported.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
No direct production impact, but functionality is intentionally not supported.

What Broke

No direct production impact, but functionality is intentionally not supported.

Why It Broke

Implemented LATENCY HISTOGRAM by throwing NotImplementedError in the client

Fix Options (Details)

Option A — Upgrade to fixed release Safe default (recommended)

pip install redis==7.1.0

When NOT to use: Do not use this fix if LATENCY HISTOGRAM support is required.

Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.

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

First fixed release: 7.1.0

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

When NOT to Use This Fix

Do not use this fix if LATENCY HISTOGRAM support is required.

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.

Version Compatibility Table

Version	Status
7.1.0	Fixed

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.