-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
0
-
2
-
None
-
3
-
TBD
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
-
0
In SERVER-103744 we added an assertion that checked the catalog instance we were using was actually the same as the latest catalog using pointer comparisons. This can fail because we have background processes that can modify the CollectionCatalog pointer even though the CollectionCatalog hasn't materially changed.
We should have an API that can compare two CollectionCatalog instances and reliably say whether they are the same.
- is related to
-
SERVER-103744 Deadlock between renameCollection, dbHash, and prepared transaction
-
- Closed
-