[SERVER-84333] Prevent a blocking sort from consuming all available disk space Created: 20/Dec/23 Updated: 30/Jan/24 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Query Execution, Stability, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ronan Merrick | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Query Execution
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Participants: | |||||
| Description |
|
With allowDiskUseByDefault defaulting to true from v6.0 onwards,have we or would we consider putting any guardrails in place to limit the size that an external sorting file can grow to, the idea being a runaway query would not be able to take down a node by exhausting all available disk space? |
| Comments |
| Comment by Kyle Suarez [ 20/Dec/23 ] |
|
Per a discussion with ilan.cohen@mongodb.com and ronan.merrick@mongodb.com on a linked ticket, it seems that we offer the possibility to limit the RAM used via a query knob but not the size of the data spilled. The server does detect when it's out of disk space but only when it's too late. Sending this to the Query Execution team for triage consideration. |