Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Query Execution
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

We should consider adding a knob that we can set to make queries stop if they exceed a certain threshold.

To start, the default value should effectively be "infinity" since there are likely many systems today which use large amounts of memory for deduping but do not experience availability problems. This knob could be used during escalations and mongotune policies to limit the amount of memory used by any one query doing RID deduplication.

is related to

SERVER-97745 [CLASSIC] OrStage should spill if allowDiskUse is specified and memory usage has exceeded some limit

Backlog

SERVER-97746 [CLASSIC] MergeSortStage should spill if allowDiskUse is specified and memory usage has exceeded some limit

Backlog

SERVER-97747 [CLASSIC] IndexScan should spill if allowDisk is specified and memory usage has exceeded some limit

Backlog

SERVER-97929 UniqueStage should spill if allowDiskUse is specified and memory usage has exceeded some limit

Backlog

SERVER-104884 UniqueRoaringStage should spill if allowDiskUse is specified and memory usage has exceeded some limit

Backlog

Assignee:: Unassigned
Reporter:: Ian Boros
Participants:: Ian Boros
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Sep 22 2025 08:14:52 PM UTC
Updated:: Sep 29 2025 04:32:02 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates