-
Type:
Task
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Storage Execution 2026-05-25
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When resuming a primary-driven index build in the collection phase that has multiple indexes, we need to make sure that we continue indexing each one from the correct spot in the collection. This is necessary because each index spills independently of the others.
- depends on
-
SERVER-126413 Ensure correct phase is persisted for PDIB
-
- Closed
-
-
SERVER-127057 Add last spilled record id to IndexStateInfo
-
- Closed
-
-
SERVER-127067 Track last record id spilled during PDIB scan
-
- Closed
-
-
SERVER-127096 Populate PDIB lastSpilledRecordId when resuming
-
- Closed
-
-
SERVER-127232 Perform all index build spilling before transitioning to load phase
-
- Closed
-
-
SERVER-127338 Use lastSpilledRecordId when determining where to resume PDIB scan
-
- Closed
-
-
SERVER-127339 Check lastSpilledRecordId when determining whether to insert key during PDIB scan
-
- Closed
-
- is depended on by
-
SERVER-126903 Test multiple indexes in PDIB jstest library
-
- In Code Review
-