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

allow_partial_results_with_maxTimeMS.js assumes find is sorted by _id, and timeout is too short

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.2.0-rc2, 6.3.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.2
    • QE 2022-11-28
    • 46

    Description

      The FindWhereSleepController in allow_partial_results_with_maxTimeMS.js assumes that find will return documents in _id order, and that tends to happen when testing locally, but that's not guaranteed by WiredTiger. We should add a .hint({_id: 1}).

      Also, ampleTimeMS was recently changed from a minimum of 2 seconds to just 100ms. This appears to be too short, and the change corresponds to the appearance of BF-26974. This timeout change should be reverted.

      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: