[SERVER-20879] Allow $group stage memory limit to be configured Created: 12/Oct/15 Updated: 02/Jun/23 Resolved: 02/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jeff Schnitzer | Assignee: | Backlog - Query Execution |
| Resolution: | Done | Votes: | 1 |
| Labels: | asya, neweng, usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Stage memory is limited to 100MB, hardcoded in document_source_group.cpp. It would be great to have this as a server-wide configuration setting instead. For dedicated analytics databases, this number should be much larger. |
| Comments |
| Comment by Asya Kamsky [ 02/Jun/23 ] |
|
Since 5.0 we have |
| Comment by Asya Kamsky [ 25/Apr/18 ] |
|
Not clear if it should be on mongod level or cluster-level or per aggregation operation limit - in case of sharded cluster it would be problematic if some of the nodes had a higher limit and others didn't and the operation failed only when it landed on some of the shards/nodes. |
| Comment by Ian Whalen (Inactive) [ 19/Jan/18 ] |
|
Should also consider handling $sort when doing this. |
| Comment by Asya Kamsky [ 17/Jan/18 ] |
|
Probably should be an internalQuery parameter that can be set through setParameter. |