[DOCS-13096] Investigate changes in SERVER-43683: Make find command with allowDiskUse option work against a view Created: 11/Oct/19 Updated: 13/Nov/23 Due: 27/Mar/20 Resolved: 31/Mar/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Jeffrey Allen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 3 years, 45 weeks, 1 day ago | ||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||
| Description |
DescriptionDownstream Change Summary Prior to this work, there was no way to specify 'allowDiskUse:true' when executing a find command against a view. This ticket (combined with work from Description of Linked TicketToday, a find command can be executed against a view which contains blocking stages like $sort or $group that can consume a lot of memory. These stages will fail at runtime if the data size exceeds some memory threshold. If the user runs an aggregate command against the view, they can specify that disk use is allowed during execution of the query. The execution engine will relieve memory consumption by spilling to disk, allowing the query to succeed. The same cannot currently be achieved with a find command. However, we recently added support for the allowDiskUse option in the find command: see related ticket Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 31/Mar/20 ] |
|
Author: {'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}Message: ( |