-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Networking
-
Fully Compatible
-
Dev Tools 2019-06-17
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.