-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: 7.0.0, 8.0.0, 8.2.0
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2026-06-22
-
1
-
🟦 Shard Catalog
-
None
-
None
-
None
-
None
-
None
-
None
I recently encountered this in some Mongosync testing and it took a bit of detective work to figure out what collection was being created inside the distributed transaction, because this was the result of an implicit create.
It'd be much easier to understand why this was happening if the namespace were included in the error response.