-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v8.0, v7.3, v7.0
-
CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05
-
0
Internal testing has hit a bug where an initial sync missed copying a collection because listDatabases failed to include the associated database. The collection and the database were created in the same transaction just before listDatabases for the initial sync, so there is a degree of concurrency involved here. We missed this collection because the collection creation also implicitly created the containing database. After committing the associated transaction but before updating the local catalog, the listDatabases command doesn't list the database.
Note: We fixed a similar issue in SERVER-82221 for listCollection.
- depends on
-
-
- Closed
-
- is depended on by
-
COMPASS-8339 Investigate changes in SERVER-90893: listDatabases inconsistent with concurrent DDL operations
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Backlog
-
-
SERVER-91861 Audit internal usage of list databases or collections for needing snapshot consistency
-
- Backlog
-