[SERVER-75376] Handle edge cases for deprioritizing unbounded user collection scans Created: 28/Mar/23  Updated: 05/Jan/24

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

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: or-workload-management
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72440 Deprioritize collection scans under load Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

As of SERVER-72440 we execute unbounded user collection scans with low storage admission priority. However there are some edge cases where we may end up deprioritizing a scan which isn't actually unbounded. For instance the following pipeline:

[{$unwind: "$foo"}, {$limit: 10}]

Such a query isn't particularly useful as it uses a limit without a sort, so we accepted this limitation for the time being. But it would be good to go through the remaining edge cases so that the behavior is consistent.


Generated at Thu Feb 08 06:30:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.