Details
-
Bug
-
Resolution: Fixed
-
Major - P3
-
None
-
None
-
None
-
Fully Compatible
-
ALL
-
Execution EMEA Team 2023-09-04, Execution EMEA Team 2023-09-18
-
35
Description
The test originally relied on the primary detecting an index inconsistency and aborting the index build from within the builder thread and replicating to the secondary. Which is why waitForIndexBuildToStop + awaitForReplication + assertIndexes guaranteed the assert on secondary would work. After graceful index builds, the secondary initiates an abort command on the primary, the index builder thread is killed, and the abort is external. So the above does not apply anymore.