redis-py How is the socket_timeout supposed to be set when

The Fix

pip install redis==7.1.0

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

@@ -909,9 +909,9 @@ class UnixDomainSocketConnection(AbstractConnection):
 
     def __init__(self, path="", socket_timeout=None, **kwargs):
+        super().__init__(**kwargs)
         self.path = path
         self.socket_timeout = socket_timeout

fix.md

Option A — Upgrade to fixed release\npip install redis==7.1.0\nWhen NOT to use: This fix should not be applied if the socket_timeout behavior is intentionally overridden elsewhere.\n\n

Why This Fix Works in Production

Trigger: How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`?
Mechanism: The socket_timeout parameter was not initialized correctly in the UnixDomainSocketConnection class
Why the fix works: The initialization of the socket_timeout parameter was fixed by adjusting the order of method calls in the UnixDomainSocketConnection class. (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.11 in real deployments (not just unit tests).
The socket_timeout parameter was not initialized correctly in the UnixDomainSocketConnection class
Production symptom (often without a traceback): How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`?

Proof / Evidence

GitHub issue: #2887
Fix PR: https://github.com/redis/redis-py/pull/3290
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.72

Discussion

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

Jump to Sources Open on GitHub

“Issue is fixed with https://github.com/redis/redis-py/pull/3290”

@petyaslavova · 2025-02-10 · source

Failure Signature (Search String)

How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`?
**Description**: I am trynig to use UDS to connect with a redis server running locally and I am getting an error regarding `self.socket_timeout` not being set. Now when I look at

Copy-friendly signature

signature.txt

Failure Signature
-----------------
How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`?
**Description**: I am trynig to use UDS to connect with a redis server running locally and I am getting an error regarding `self.socket_timeout` not being set. Now when I look at the API it is as follows

Error Message

Signature-only (no traceback captured)

error.txt

Error Message
-------------
How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`?
**Description**: I am trynig to use UDS to connect with a redis server running locally and I am getting an error regarding `self.socket_timeout` not being set. Now when I look at the API it is as follows

Environment

Python: 3.11

What Broke

Users experienced connection errors due to the socket_timeout not being set when using Unix domain sockets.

Why It Broke

The socket_timeout parameter was not initialized correctly in the UnixDomainSocketConnection class

Fix Options (Details)

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

pip install redis==7.1.0

When NOT to use: This fix should not be applied if the socket_timeout behavior is intentionally overridden elsewhere.

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

First fixed release: 7.1.0

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

When NOT to Use This Fix

This fix should not be applied if the socket_timeout behavior is intentionally overridden elsewhere.

Did This Fix Work in Your Case?

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

Prevention

Track RSS + object counts after deployments; alert on monotonic growth and GC pressure.
Add a long-running test that repeats the failing call path and asserts stable memory.
Make timeouts explicit and test them (unit + integration) to avoid silent behavior changes.
Instrument retries (attempt count + reason) and alert on spikes to catch dependency slowdowns.

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.

redis-py How is the socket_timeout supposed to be set when using `UnixDomainSocketConnection`? (Fix)