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

Investigate a way to deal with pre-evaluation errors in optimization agg-fuzzer

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.4
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • Fully Compatible
    • TIG 2018-09-24, STM 2018-10-08

      When running aggregation, the aggregation framework will pre-evaluate some of the arguments. During that pre-evaluation, it may encounter and throw an error. If optimizations are disabled via failpoints, however, the pre-evaluation phase does not happen and the error is not hit, instead the aggregation simply returns no documents.

      As a result, when the aggregation fuzzer is run in optimization mode, it frequently hits this discrepancy (one mongod throws an error and another returns 0 documents).

      One possible solution from charlie.swanson would be to add context to the error messages hit during pre-evaluation. The fuzzer could then check for that context and validate accordingly.

      This ticket is to investigate what it would take to implement that solution (or another solution if appropriate), make any needed changes to the mongo repo and open a ticket to update the aggregation fuzzer.

            Assignee:
            robert.guo@mongodb.com Robert Guo (Inactive)
            Reporter:
            david.bradford@mongodb.com David Bradford (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: