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

dbCheck tests should tolerate non-deterministic batch boundaries

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-04-04
    • 38

    Description

      dbCheck evaluates exit conditions like maxCount and maxSize at batch boundaries. The batch boundaries are not necessarily deterministic, e.g. they can be time-bound via maxBatchTimeMillis.

      For example, on a collection with _id values starting from 0 and increasing incrementally, a dbCheck run with a batch size of 1000 docs and maxCount (i.e. number of documents to scan to reach completion) of 5000, won't necessarily complete when reaching the upper batch boundary _id:5000. It will instead complete with an upper boundary of 5000 or greater. This is because an interim batch may complete before reaching 1000 documents, and because the dbCheck exit condition is evaluate between batches.

      Attachments

        Activity

          People

            josef.ahmad@mongodb.com Josef Ahmad
            josef.ahmad@mongodb.com Josef Ahmad
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: