Operational Defect Database
BugZero found this defect 110 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2561710
establishConsistentCollections with timestamp not consistent
Last update date:
3/14/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
establishConsistentCollections (that seems to establish consistent database) does not establish a consistent view of the database when a timestamp is provided. It uses the latest state of the collection catalog to determine which collections might exist and establishes a correct snapshot for them. However, collections that existed at the timestamp but has since been dropped would be missed. We don't seem to use this with a timestamp so I suggest we remove the timestamp parameter to keep this simple. If the desire is to establish a consistent database we'd need to traverse _nss in the historical catalogId tracker and filter on namespace and existence for a complete set of collections at the given time.
Top User Comments
Steps to Reproduce
