[SERVER-66162] ConnectionPool getConnection may shorten specified connection timeout Created: 03/May/22  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Daniel Morilha (Inactive) Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-43155 Queries which exceed maxTimeMS may re... Closed
Assigned Teams:
Service Arch
Operating System: ALL
Steps To Reproduce:

1. Remove ConnectionPool shortening timeout.
2. Trigger an evergreen build (here is a recent one)
3. Analyze crashes for ConnectionPoolTest::SetupTimeoutsDontTimeoutUnrelatedRequests

Participants:
Story Points: 2

 Description   

ConnectionPool::getConnection accepts one parameter to set how many milliseconds a connection can take, however the logic within may shorten the timeout to the controller's pending timeout.

During multiple discussion it isn't clear if this is still needed and why, removing it causes few ConnectionPool executor_tests fail.

amirsaman.memaripour@mongodb.com also brought up the point that it doesn't make much of a difference when this method, which is purely responsible for acquiring a connection to its peer, take longer than 20 seconds.

The acceptance criteria for this ticket is to define if ConnectionPool should interfere with its given timeout, and if not, remove it.


Generated at Thu Feb 08 06:04:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.