-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-11-23
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The stack makes container sorters spill incrementally unconditionally, so there is nothing to enable by default and no kill switch: the fallback is a revert.
The index-build write path is hot, so before any merge the stack is measured with a sys-perf run comparing a base build against a patched build (no off/on arms): flow-control engagement and standby lag should improve as in SERVER-132056's measurements, sorter memory should stay within the budget, and the foreground p50 change should be re-checked.
- split from
-
SERVER-132056 Investigate incremental spilling in primary-driven index builds
-
- Closed
-