BugZero found this defect 38 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
4/11/2024
MongoDB Server
No affected releases provided.
8.0 Required
The issue is coming from the following events: A collection cloning starts on the syncing shard Index build starts on the syncing shard (_id_) Collection dropped on the primary shard Index build stops on the syncing shard (_id_) Uncommitted indices get dropped on the syncing shard Oplog replay begins on the syncing shard An oplog entry relies on the _id_ index on the syncing shard Crash The regression is coming from SERVER-78615 The suggested solution is to not to perform modifications on views while initial data sync happens, and when onInitialDataAvailable happens, reload the views