-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
Service Arch 2019-01-14, Service Arch 2019-01-28
-
0
jstests/core/txns/write_conflicts_with_non_txns.js runs an insert with maxTimeMS that is expected to hit the maxTimeMS limit because of WriteConflict errors, but the insert never returns when the test is run against mongos, because the maxTimeMS is not forwarded to the shard and mongos doesn't seem to check for interrupts in the batch write path. This is probably an issue for cluster update and delete as well.
This test can't be run in the sharded core txns suite because of this.
- is related to
-
SERVER-46187 MongoS doesn't pass maxTimeMS to shards for write commands
- Closed
-
SERVER-46188 Blacklist write_conflicts_with_non_txns.js from sharded transaction passthrough suites due to maxTimeMS incompatibility
- Closed