Handle QueryMemoryTracking feature flag with multiversion testing

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • Fully Compatible
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-111011 made the change to test whether the explain output uses the new 
      peakTrackedMemBytes instead of maxTotalMemoryUsageBytes. This broke during multiversion sharded cluster testing due to the test being strict on output based on feature flag value. This check needs to be relaxed and moved to a non-multiversion testing.

            Assignee:
            Calvin Nguyen
            Reporter:
            Calvin Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: