[SERVER-58726] Test spilling behavior for new set of accumulators Created: 21/Jul/21  Updated: 29/Oct/23  Resolved: 08/Nov/21

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

Type: Task Priority: Major - P3
Reporter: Mihai Andrei Assignee: Mihai Andrei
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: QE 2021-11-01, QE 2021-11-15
Participants:

 Description   

This ticket is responsible for adding test coverage around spilling to disk for the new exact top-n accumulators. In particular:

  • Add tests to verify that spilling works correctly for the exact top-n accumulators in jstests/aggregation/spill_to_disk.js
  • Add tests to verify that the 'internalQueryMaxNAccumulatorBytes' memory limit is obeyed in jstests/noPassthrough/agg_configurable_memory_limits.js (that is, if this configured to a low value, any top-n operation will fail).

Additionally, we should consider updating the error messages for the variousĀ 'ExceededMemoryLimit' uasserts added as part of this project. Specifically, they should clarify that an error was raised because too much memory was used and spilling would not help.



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

Author:

{'name': 'Mihai Andrei', 'email': 'mihai.andrei@10gen.com', 'username': 'mtandrei'}

Message: SERVER-58726 Test spilling behavior for exact top-n accumulators and fix serialization logic for merging on a shard
Branch: master
https://github.com/mongodb/mongo/commit/e1c33dfc0edc4d52062e4349bf07357105bafdac

Comment by Kyle Suarez [ 27/Oct/21 ]

mihai.andrei, would it make sense to track the separate spilling-to-disk issue and its fix in a separate SERVER ticket?

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