-
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 container spiller always spills incrementally: SERVER-138779's two-buffer machinery is always on, decided in the SERVER-132056 review, so there is no parameter to add and no wiring in makeSpiller.
This adds incremental_sorter_spilling.js to the no_passthrough_primary_driven_index_builds matrix suite. The collection is sized so the scan spills many times against the minimum sorter memory budget, and the insertion batch size is small enough that each spill is emitted in many batches, so the incremental path is exercised end to end. The test asserts the build spilled and that the resulting index is complete and usable.
- is related to
-
SERVER-138780 Add resumable index build coverage for incremental spilling
-
- Open
-
-
SERVER-138779 Give NoLimitSorter two swapping buffers for incremental spilling
-
- In Code Review
-
-
SERVER-132056 Investigate incremental spilling in primary-driven index builds
-
- Closed
-
-
SERVER-138778 Add incremental spilling support to Spiller and ContainerBasedSpiller
-
- Closed
-
- split from
-
SERVER-138779 Give NoLimitSorter two swapping buffers for incremental spilling
-
- In Code Review
-