SERVER-137197ClosedFixed

Resume primary-driven index builds when the resume record has been deleted

When a primary-driven index build resumes after a failover, its collection scan seeks to exactly the smallest lastSpilledRecordId across the build's indexes. If that document was deleted before the resume, for example by capped collection roll-off or a user delete, the seek fails with KeyNotFound and the new primary aborts the build. The scan should instead start at the first remaining record at or after the resume point, which is safe because the deleted documents' keys are removed when the sid

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue
Index Builds
Labels
Tags and classification

No labels assigned.