[SERVER-35797] NetworkInterfaceExceededTimeLimit error messages should include the timeout value Created: 25/Jun/18  Updated: 29/Oct/23  Resolved: 13/Jun/19

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

Type: Improvement Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Alya Berciu
Resolution: Fixed Votes: 1
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Dev Tools 2019-06-17
Participants:

 Description   

When a network request running on a TaskExecutor times out with a NetworkInterfaceExceededTimeLimit code, the error message doesn't seem to include the actual timeout duration that was exceeded. For example, the "Couldn't get a connection within the time limit" error message generated here doesn't include the timeout value in the message. This would be nice to include to help understand why network requests are timing out, when we print out error codes and messages in mongod logs, for example.



 Comments   
Comment by Billy Donahue [ 10/Jul/19 ]

Yes of course.

We just pulled this from the Dev Tools “Neweng” backlog and thought it was
“ours”.

Sorry for the surprise!

Comment by Githook User [ 13/Jun/19 ]

Author:

{'name': 'Alya Berciu', 'email': 'alya.berciu@mongodb.com', 'username': 'alyacb'}

Message: SERVER-35797 Add timeout value to NetworkInterfaceExceededTimeLimit messages
Branch: master
https://github.com/mongodb/mongo/commit/f90df932ab3f8c5f279b6f14343fe0efa80c1b9a

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