Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36124

Mongos does not obey maxTimeMS for inserts

XMLWordPrintableJSON

    • 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.

            Assignee:
            mathias@mongodb.com Mathias Stearn
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: