-
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
Interrupting a build mid-collection-scan with committed-but-unpersisted spill batches is the case the captured resume position must survive: the resumed scan re-adds everything after lastSpilledRecordId and must not lose keys.
This parameterizes the resumable scan-phase jstests with incremental spilling enabled and asserts no keys are lost via full validate, replicated hashes, and per-key lookups. The knob stays off for resumable builds until these pass.
- is related to
-
SERVER-138778 Add incremental spilling support to Spiller and ContainerBasedSpiller
-
- Closed
-
- related to
-
SERVER-139235 Add incremental_sorter_spilling.js end-to-end jstest
-
- In Progress
-
- split from
-
SERVER-132056 Investigate incremental spilling in primary-driven index builds
-
- Closed
-