-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Querying
-
None
-
Service Arch
-
Fully Compatible
-
v6.0, v5.0
-
Service Arch 2022-04-18, Service Arch 2022-05-02, Service Arch 2022-05-16, Service Arch 2022-05-30, Service Arch 2022-06-13, Service Arch 2022-06-27, Service Arch 2022-07-11
-
17
In shard_remote, the maxTimeMS of a query is used as a request timeout. If the time limit is exceeded by the network layer, "NetworkInterfaceExeededTimeLimit" will be returned instead of MaxTimeMSExpired. (e.g. here, here).
- is related to
-
SERVER-63181 Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware
- Closed
- related to
-
SERVER-66162 ConnectionPool getConnection may shorten specified connection timeout
- Open
-
SERVER-63181 Make ConnectionPool::SpecificPool::updateEventTimer topology reconfiguration aware
- Closed
-
SERVER-65472 Relax time out error code in timeseries_coll_mod.js
- Closed
-
SERVER-67722 Shard cursor is not killed on MaxTimeMSExpired
- Closed
-
SERVER-79888 find/getMore timeouts triggered by Fetcher always reported as NetworkInterfaceExceededTimeLimit
- Needs Scheduling
- split to
-
SERVER-66260 Modify executor::RemoteCommand object to accept an option argument
- Closed