Details
-
Improvement
-
Resolution: Unresolved
-
Major - P3
-
None
-
None
-
None
-
None
-
Catalog and Routing
-
1
Description
If there is an error during the commit phase of the create collection, we are going to check if the collection is already committed to the config server to advance to the following phase, i.e. being idempotent.
Today, to check if the collection is already committed we use checkIfCollectionAlreadyTrackedWithOptions. It is correct, but also unnecessary.
With the create collection coordinator, we have the guarantees to not register another collection with different options working on the same namespace. With that, it is only necessary to check if the collection exists in the sharding catalog to advance to the following phase of the coordinator.
The goal of this ticket is to improve that part of the code, by changing the call checkIfCollectionAlreadyTrackedWithOptions to only check if the collection already exists in the sharding catalog of the config server.