[SERVER-36124] Mongos does not obey maxTimeMS for inserts Created: 13/Jul/18 Updated: 29/Oct/23 Resolved: 23/Jan/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Mathias Stearn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:RouterSupport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Service Arch 2019-01-14, Service Arch 2019-01-28 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 23/Jan/19 ] |
|
Author: {'email': 'mathias@10gen.com', 'name': 'Mathias Stearn', 'username': 'RedBeard0531'}Message: |