-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0-rc0, 7.3.0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
Given a replica set with a direct connection on it, once the replica-set is added to the cluster the collections in it will be registered to the CSRS.
However, if the direct connection is not dropped, dropping the collection via direct connection and re-creating it via mongos will cause a uuid inconsistency
The createCollectionCoordinator relies that the collection is always present both on the local catalog of the primary and on the sharding catalog.
In this case, the coordinator believes the collection does not exists because it's not present locally. It will proceed to create locally a new collection with a different uuid.
During the commit phase, it will fail to upsert the previous collection as the new uuid is used to find the existing document