Raise default timeouts for sharding in tests

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • Cluster Scalability 2024-11-11
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      There are a handful of timeouts with defaults that can lead to spurious test failures on slow machines, like the default maxTimeMS of 30 seconds for many internal sharding queries or the 5ms transaction lock acquisition timeout.

      Note the maxTimeMS is already raised in many suites, but on a per suite basis, which omits some tests. Instead we should raise the timeout in a more generic way, like via standalone.py or servers.js.

            Assignee:
            Jack Mulrow
            Reporter:
            Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: