[SERVER-61651] Always check HashAgg memory limit in UnionWith.js test Created: 19/Nov/21  Updated: 29/Oct/23  Resolved: 30/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: Backlog
Fix Version/s: 5.2.0

Type: Bug Priority: Major - P3
Reporter: Eric Cox (Inactive) Assignee: Eric Cox (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2021-11-29, QE 2021-12-13
Participants:

 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.



 Comments   
Comment by Githook User [ 22/Nov/21 ]

Author:

{'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}

Message: SERVER-61651 Always check HashAgg memory limit in UnionWith.js test
Branch: master
https://github.com/mongodb/mongo/commit/337e43030afb6de83a2e3ed25575ec8874a70d20

Generated at Thu Feb 08 05:52:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.