BugZero found this defect 67 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
3/15/2024
MongoDB Server
No affected releases provided.
No fixed releases provided.
The oplog is reportedly an exception to our catalog concurrency rules and updates its metadata in place. CollectionImpl::getCollectionOptions does not handle the oplog's special case and wrongly reads the oplog metadata as if it weren't updated in place. As a consequence, we have observed a race between resizing the oplog and the FTDC controller periodically sampling the oplog metadata. We should, at minimum, serialise getting the collection options for the oplog and audit the other metadata APIs for other possible oplog accesses.