-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2024-09-30, CAR Team 2024-10-14, CAR Team 2024-10-28, CAR Team 2024-11-11, CAR Team 2024-11-25, CAR Team 2024-12-09
In CommonProcessInterface::refreshAndGetCollectionVersion we decide to discard the collection version when ChunkManager::isSharded() is false.
I have the feeling this is wrong and in fact for a tracked unsharded collection ChunkManager::isSharded() will be false but since the collection is tracked it also has a collection version that should not be discarded.
More generally, I'm wondering why do we need to expose a function in the CommonProcessInterface to force a refresh and get the collection version.
- related to
-
SERVER-95749 Avoid force collection cache refresh in MongosProcessInterface::ensureFieldsUniqueOrResolveDocumentKey
-
- Needs Scheduling
-