Increase defaultMaxTimeMS value to avoid zero remaining time sent to shards in jstest

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0, 8.0.0-rc9
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • v8.0
    • CAR Team 2024-06-10
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We use maxTimeNeverTimeOut failpoint on mongos to avoid timing out before the command reaching the shards. But if the default timeout value is small, it could be used up on mongos and the value zero could be sent which means "do not time out". This can lead to test cases which are expected to fail to pass. We should give it enough time on the router to avoid this scenario.

              Assignee:
              Yuhong Zhang
              Reporter:
              Yuhong Zhang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: