-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Fully Compatible
-
ALL
-
-
Service arch 2020-05-04, Service arch 2020-05-18, Service arch 2020-06-01, Service arch 2020-06-15, Service arch 2020-06-29, Service arch 2020-07-13, Service Arch 2020-07-27, Service Arch 2020-08-10, Service Arch 2020-08-24, Service arch 2020-09-07
-
0
When running an insert through a mongoS it appears that a MaxTimeMSExpired error can be returned to the client even if the operation is still running on a shard mongod. This behavior seems unexpected and undesirable if a client expects that a maxTimeMS timeout error implies an operation has failed with no effect.
- depends on
-
SERVER-49872 Allow the maxTimeAlwaysTimeOut FailPoint to ignore certain commands
- Closed
- related to
-
SERVER-36124 Mongos does not obey maxTimeMS for inserts
- Closed
-
SERVER-46188 Blacklist write_conflicts_with_non_txns.js from sharded transaction passthrough suites due to maxTimeMS incompatibility
- Closed
-
SERVER-47972 maxTimeMS set on hedged requests does not give shards enough time to refresh
- Closed
-
SERVER-50645 Complete TODO listed in SERVER-46187
- Closed