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

Always check HashAgg memory limit in UnionWith.js test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.2.0
    • Backlog
    • None
    • None
    • Fully Compatible
    • ALL
    • QE 2021-11-29, QE 2021-12-13

    Description

      It looks like a unionWith query should have reached the memory limit and failed when $group is pushed down, but it suceeded. This is most likely due to the difference in reporting the memory limit in HashAgg as it differs from the classic engine.

      https://logkeeper.mongodb.org/lobster/build/f1bc993303085d81713acaa781df07b1/test/6195b3b39041307c2347fe84#bookmarks=0%2C34%2C180&l=1

      The investigator should verify this and determine if the test can be changed or we need to revisit memory usage checks in hashAgg.

      Attachments

        Activity

          People

            eric.cox@mongodb.com Eric Cox (Inactive)
            eric.cox@mongodb.com Eric Cox (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: