Make allow_partial_results_with_maxTimeMS_failpoints.js robust to machine slowdowns

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • ALL
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In BF-35161, a slowdown in MacOs cause this failing test which checks that with 'allowPartialResults: true', if one shard times out due to a network error the other will still return results. When allowPartialResults is true, we allot 75% of the time to gathering the results and 25% to process if we need to return partial results here. When macOS slowed down, the 25% of the time budget was insufficient to process everything and mongos would timeout here. We should consider future-proofing this test so this doesn't happen with for future possible machine slowdowns.

              Assignee:
              Unassigned
              Reporter:
              Kristina Znam
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: