A primary node that steps down with an ongoing index build may affect new index builds containing the same index names as a secondary.
If the interrupted index build started when the node was a primary is slow to complete its teardown, it may conflict with new index builds triggered by the createIndexes oplog entry due to the IndexBuildAlreadyInProgress check in the IndexBuildsCoordinator. This error is considered non-fatal during oplog application and would result in the secondary node silently ignore the index creation request.
This issue affects index builds started on a primary that is using the IndexBuildsCoordinator so we should not see this same failure under 4.2.
Also, this issue should go away with two phase index builds but may still be observer under FCV 4.2 when we trigger index builds on the createIndexes oplog entry.
- is depended on by
-
SERVER-43692 enable two phase index builds by default
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
- related to
-
SERVER-43826 Coverity analysis defect 113598: PW.PARAMETER_HIDDEN
-
- Closed
-