-
Type: Task
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Index Maintenance
-
None
We do an untimestamped write when writing the resume info to disk on a clean shutdown. If the startIndexBuild oplog entry has an optime after the stable timestamp at shutdown, it might be possible to read the resume info and try to resume the index build even though we'll see the oplog again when replaying the oplog (and start the index build there). We should to investigate if this is possible or not.
- is related to
-
SERVER-39225 Update kill_rooted_or.js / IndexBuildsCoordinator to gracefully handle index build already in-progress errors
- Closed
-
SERVER-39369 Filter index builds requests in the coordinator, register the builds on the Coordinator and set them up in the persisted catalog before changing threads
- Closed
-
SERVER-47291 Execution Architecture Guide: Startup Recovery
- Closed