[SERVER-63181] Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware Created: 01/Feb/22  Updated: 06/Dec/22  Resolved: 14/Apr/22

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

Type: Bug Priority: Major - P3
Reporter: Daniel Morilha (Inactive) Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: sa-remove-fv-backlog-22
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-43155 Queries which exceed maxTimeMS may re... Closed
is related to SERVER-43155 Queries which exceed maxTimeMS may re... Closed
Assigned Teams:
Service Arch
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

BF-20554 surfaced a problem where ConnectionPool::SpecificPool::updateEventTimer might incorrectly trigger deferredStateUpdateFunc while a topology reconfiguration is happening in the shard leading to client's DoS.

The logic might have to consider when a topology reconfiguration happens and act appropriately.

AC: After exceeding kHostRetryTimeout (currently hardcoded to 1 second), log how long it takes for getting a connection within the time limit before raising ErrorCodes::NetworkInterfaceExceededTimeLimit



 Comments   
Comment by Daniel Morilha (Inactive) [ 14/Apr/22 ]

It turns out the error isn't appropriated to this condition at all.

Generated at Thu Feb 08 05:57:05 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.