-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
PyMongo follows the SDAM spec for handling network timeouts and other errors when attempting an operation, but it does not follow the spec when first creating a new socket connection. A call to pool.get_socket that fails due to a network timeout should result in the server that pool belongs to being reset, with a descriptive error added to the server's error field. See the spec clarification here:
https://github.com/mongodb/specifications/commit/bfddbd98bf396104f78500f93f1f13e3fd2d8c3a
- is depended on by
-
DRIVERS-429 Change handling of network errors or timeouts during connection handshake
- Closed
- is duplicated by
-
PYTHON-2211 MongoClient does not mark a server unknown when connection handshake fails with a network timeout error
- Closed
- related to
-
PYTHON-1672 Implement Connection Monitoring and Pooling spec
- Released