redis-py [Question] Remove Redis Cluster logs (Fix)

The Fix

pip install redis==7.1.0

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

Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.

Open PR/Commit

@@ -1,4 +1,4 @@
@@ -1,4 +1,4 @@
-
+    * Remove verbose logging from cluster.py
     * Add retry mechanism to async version of Connection

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: This fix is inappropriate if the application relies on the existing logging behavior for debugging.\n\n

Why This Fix Works in Production

Trigger: There is so much logs in `cluster` module that I would not want it to show up in my application logs. Is there a reason to leave these logs in this module?…
Mechanism: Verbose logging in the cluster module adds unnecessary overhead and clutter to application logs
Why the fix works: Removes verbose logging from the cluster module in redis-py, addressing concerns raised in issue #2227. (first fixed release: 7.1.0).

Production impact:

If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.

Why This Breaks in Prod

Shows up under Python 3.8.10 in real deployments (not just unit tests).
Verbose logging in the cluster module adds unnecessary overhead and clutter to application logs
Production symptom (often without a traceback): There is so much logs in `cluster` module that I would not want it to show up in my application logs. Is there a reason to leave these logs in this module? Instead, couldn't we just raise exception and let the user handle them as he wishes?

Proof / Evidence

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

Discussion

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

Jump to Sources Open on GitHub

“I think that would be best”

@utkarshgupta137 · 2022-06-17 · source

“Agreed. Those shouldn't have made it through the PR. However, I'd argue that this is a breaking (but worthwhile!) change, in case someone is relying…”

@chayim · 2022-06-15 · source

“In theory, are we saying here that we would like to remove all of the log. statements from *redis-py/redis/cluster.py*?”

@nialdaly · 2022-06-17 · source

“Hi @utkarshgupta137 @chayim @Ankhas I made some changes to redis-py/redis/cluster.py in this PR. Hopefully it looks okay!”

@nialdaly · 2022-06-18 · source

Failure Signature (Search String)

There is so much logs in `cluster` module that I would not want it to show up in my application logs. Is there a reason to leave these logs in this module? Instead, couldn't we
Agreed. Those shouldn't have made it through the PR. However, I'd argue that this is a breaking (but worthwhile!) change, in case someone is relying on this behaviour.

Copy-friendly signature

signature.txt

Failure Signature
-----------------
There is so much logs in `cluster` module that I would not want it to show up in my application logs. Is there a reason to leave these logs in this module? Instead, couldn't we just raise exception and let the user handle them as he wishes?
Agreed. Those shouldn't have made it through the PR. However, I'd argue that this is a breaking (but worthwhile!) change, in case someone is relying on this behaviour.

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
There is so much logs in `cluster` module that I would not want it to show up in my application logs. Is there a reason to leave these logs in this module? Instead, couldn't we just raise exception and let the user handle them as he wishes?
Agreed. Those shouldn't have made it through the PR. However, I'd argue that this is a breaking (but worthwhile!) change, in case someone is relying on this behaviour.

Environment

Python: 3.8.10

What Broke

Excessive logging can lead to performance degradation and increased log storage costs.

Why It Broke

Verbose logging in the cluster module adds unnecessary overhead and clutter to application logs

Fix Options (Details)

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

pip install redis==7.1.0

When NOT to use: This fix is inappropriate if the application relies on the existing logging behavior for debugging.

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/2238

First fixed release: 7.1.0

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

When NOT to Use This Fix

This fix is inappropriate if the application relies on the existing logging behavior for debugging.

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:configuration-error redis-py hub redis-py best practices All hubs All clusters

Related clusters: Retry storm Data consistency Race condition

Sources

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