For resumable index builds, in order to ensure that we do not need to roll back any of the keys inserted into the sorter, the collection scan should start at a timestamp that has been majority committed. We will also need to ensure that the side writes table doesn't miss any writes. When we initially begin the collection scan, we must first install the side writes interceptor and then wait for the last oplog entry (the last entry that was not captured by the interceptor) to become majority committed, before establishing the snapshot to read the collection.
- related to
-
SERVER-50360 ValidateStateTest::OpenCursorsOnAllIndexes fails when resumable index builds are enabled
- Closed
-
SERVER-50366 StorageTimestampTests::TimestampIndexBuilds<true> fails when resumable index builds are enabled
- Closed
-
SERVER-50391 Index build hung during startup recovery waiting for optime to be majority committed
- Closed
-
SERVER-50446 make index builds non-resumable when commit quorum is disabled
- Closed
-
SERVER-50519 resumable index build hangs waiting for majority commit point in replica_sets_kill_secondaries_jscore_passthrough
- Closed
-
SERVER-49075 Add replica_sets suite to resumable index build variant
- Closed
-
SERVER-49076 Add rollback fuzzer suites to resumable index build variant
- Closed
-
SERVER-49083 Make noPassthrough tests work with resumable index builds
- Closed
-
SERVER-49774 Enable rollback testing for resumable index builds in the collection scan phase
- Closed
-
SERVER-50539 extend resumable index build majority wait to support deadline
- Closed