[SERVER-46866] NetworkInterfaceExceededTimeLimit 'timeout' in logs is misleading Created: 13/Mar/20  Updated: 03/Aug/23  Resolved: 17/Jun/20

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

Type: Bug Priority: Minor - P4
Reporter: Randolph Tan Assignee: Backlog - Service Architecture
Resolution: Duplicate Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-48511 Improve ConnectionPool error messages Closed
Assigned Teams:
Service Arch
Operating System: ALL
Participants:

 Description   

https://github.com/mongodb/mongo/blob/f3a8b79683137be0f8256358a4d424fa88ebfda7/src/mongo/executor/connection_pool.cpp#L1115

The timeout that ends up being logged is not the timeout of the request (ie, the total time request spent) but it appears to be the time in between the last time ConnectionPool::SpecificPool::updateEventTimer was called and the request with the earliest expiration.



 Comments   
Comment by Amirsaman Memaripour [ 17/Jun/20 ]

SERVER-48511 addresses the concern introduced in this ticket.

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