Supported mongos commands should propagate maxTimeMS option to shards

XMLWordPrintableJSON

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

      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
              Reporter:
              Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: