Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-70931

allow_partial_results_with_maxTimeMS_failpoints.js can set very short timeouts

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • QE 2022-10-31
    • 35

    Description

      In BF-26761 and BF-26762, allow_partial_results_with_maxTimeMS_failpoints.js runs some find queries with a maxTimeMS timeout of only 30ms or 40ms, which does not leave enough margin for delays due to resource contention. This is controlled via the ampleTimeMS variable, which was being set to 10x the runtime of some query. When I wrote the test and tested locally, I was seeing ampleTimeMS values around 5 seconds. Evergreen environments are just a lot faster in some cases (probably due to using optimized instead of debug builds).

      To make this test more robust, and hopefully address those BFs, we should lower-bound ampleTimeMS with some more conservative value, like one second.

      Attachments

        Activity

          People

            steve.tarzia@mongodb.com Steve Tarzia
            steve.tarzia@mongodb.com Steve Tarzia
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: