-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
v8.0
-
200
The meaning of this error was modified slightly as a result of refactoring in the network interface code. It is now considered a general timeout error, and the sharding code should not always make the server unavailable if this error occurs.
- depends on
-
SERVER-80020 The exhaustiveFindOnConfig() method should retry on NetworkInterfaceExceededTimeLimit errors
- Backlog
-
SERVER-81877 ShardRemote::_scheduleCommand can update RPC timeout to use OpCtx timeout but doesn't update error code
- Backlog
-
SERVER-79888 find/getMore timeouts triggered by Fetcher always reported as NetworkInterfaceExceededTimeLimit
- Investigating
- is related to
-
SERVER-72055 NetworkInterfaceTL should by default return a retryable error when it times out waiting to acquire a connection
- Closed