Unfinished index builds are not restarted in standalone mode. When the server is started with --recoverFromOplogAsStandalone, a commitIndexBuild oplog entry during oplog recovery is a no-op for these unfinished indexes. This has the potential to hang oplog recovery when replaying oplog entries after the commitIndexBuild oplog entry, like renameCollection with dropTarget=true which checks that there are no index builds in progress.
'commitIndexBuild' oplog entry is a no-op for unfinished index builds not restarted
- Votes:
-
0 Vote for this issue
- Watchers:
-
5 Start watching this issue
- Created:
- Updated:
- Resolved: