[DOCS-6177] Request for addition: explicit sharded memory limits for the aggregation pipeline Created: 10/Sep/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Cross | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Description |
|
The memory usage limit for the aggregation pipeline is 100 MB. For a sharded cluster, this happens in two stages: a distributed stage on the various shards, and a final stage on the primary shard for the database. We should mention that the 100 MB limit is a per-server limit, so for the first (distributed) stage, it can be more. Also, I haven't checked this, so please verify it with someone in the know if you do plan to publish it; I'm only 80% sure. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |