allow_partial_results_with_maxTimeMS_failpoints.js can timeout before getMore

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Hide

      I have not reproduced this locally, because it seems to require competing tasks to consume resources in the background, but we have a cold BF that suggests this is happening: BF-26792.

      Show
      I have not reproduced this locally, because it seems to require competing tasks to consume resources in the background, but we have a cold BF that suggests this is happening: BF-26792.
    • QE 2022-12-12, QE 2022-12-26
    • 16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      As seen in BF-26792, it's possible for allow_partial_results_with_maxTimeMS_failpoints.js to unexpectedly return a MaxTimeMSExpired error on the initial find (line 289) of the test that looks for timeouts in a getMore.  This happens in roughly 5% of evergreen runs, probably when resources are limited after the ampleTimeMS is calculated.

      To avoid this unexpected timeout, we can set the "maxTimeNeverTimeOut" failpoint.

            Assignee:
            Steve Tarzia
            Reporter:
            Steve Tarzia
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: