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

Supported mongos commands should propagate maxTimeMS option to shards

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.5.3
    • Component/s: None
    • ALL

      In sharded cluster, mongos commands supported by maxTimeMS should propagate the maxTimeMS option to shards. However, the following commands don't satisfy this contract.

      1. fsync
      2. movePrimary. Before the metadata on config server is changed by movePrimary, it is interruptible.

            Assignee:
            Unassigned Unassigned
            Reporter:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: