Operational Defect Database
BugZero found this defect 94 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2577521
CollectionRoutingInfo could contain stale database information even after refresh
Last update date:
3/15/2024
Affected products:
MongoDB Server
Affected releases:
5.0.0
6.0.0
7.0.0
7.3.0-rc0
8.0.0-rc0
Fixed releases:
No fixed releases provided.
Description:
Info
CollectionRoutingInfo contains information about both the collection and the database. The "get.*CollectionRoutingInfoWithRefresh()" functions of the CatalogCache guarantees that the collection information contained in the returned CollectionRoutingInfo object are causal consistent with respect to the latest config time known by the node. While this is true for collection information, it is not true for the database information contained in the object, namely database version and database primary shard. This is because those withRefresh functions only advance the time in store for the collection cache entry but not for the database. This means that it is not safe to use the database information stored in the CollectionRoutingInfo when executing in either Shard or DDL role.
Top User Comments
Steps to Reproduce
