In PYTHON-5202 we discovered a bug where pymongo would clear the pool after a WaitQueueTimeoutError. This is problematic because WaitQueueTimeoutError is likely to happen when the system is under heavy load and clearing the pool will make that worse (since connections needs to be recreated).
We should add a unified spec test to ensure wait queue timeout errors do not clear the pool.
- related to
-
PYTHON-5202 WaitQueueTimeoutError causes pool to be cleared
-
- Closed
-
- split to
-
CDRIVER-5928 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
CSHARP-5524 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
CXX-3248 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
GODRIVER-3505 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
JAVA-5815 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
NODE-6857 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
PHPLIB-1644 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
RUBY-3633 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
RUST-2178 Test that wait queue timeout errors do not clear the pool
-
- Blocked
-
-
PYTHON-5208 Test that wait queue timeout errors do not clear the pool
-
- In Progress
-
-
MOTOR-1442 Test that wait queue timeout errors do not clear the pool
-
- Closed
-