-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 8.1.0-rc0, 6.0.16, 7.0.12, 7.3.4, 8.0.0-rc12
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
v8.0, v7.3, v7.0, v6.0
-
CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02
-
200
Detailed description and repro in the attached BF.
In the shard role api, we call resolveNamespaceStringOrUUID before establishing a consistent collection in order to determine which read source we should be using. However, lookupNSSByUUID does not check the commit pending uuid list. This results in the namespace resolution throwing NamespaceNotFound for commit pending namespaces.
As part of this ticket, we should also audit the other functions in the collection catalog to determine whether they should also be checking the commit pending lists to prevent similar problems from popping up in the future.
- related to
-
SERVER-92273 ListCollections has inconsistent behavior for commit pending namespaces (7.0 only)
- In Code Review
-
SERVER-92371 Read commands on non-existing collections return different results with Namespace or UUID
- Closed
-
SERVER-93691 [v8.0] Revert "SERVER-82221 listCollections and listIndexes should include commit-pending namespaces"
- Closed
-
SERVER-93695 Add concurrency suite that tests with random catalog commit delays
- Closed