BugZero found this defect 19 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/30/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
In the following series of events: Index build starts. It is journaled and written to the oplog. Node is shutdown uncleanly A checkpoint was not taken The node can be left in a state at startup where the index build does not exist on the catalog but exists in the oplog. This can be a problem when a problematic index build is the cause of unclean shutdown as we'll likely end up in a restart loop (node crashes during startup from the index build, restarts, crashes again). We are unable to drop the index build in standalone because it is not reconciled to the catalog. recoverFromOplogAsStandalone=true is also unhelpful in this case as it is a read-only mode and thus unable to drop the index while the problematic index build is in progress.