-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
Similarly to SERVER-86593 if the dataShard parameter is specified when trying to create an unsplittable collection, and we use the shard URL instead of the shard name, the create collection coordinator will commit the collection metadata in the config server, but the collection will be unreachable from the cluster. You can find a reproducible attached to the ticket.
We should use something similar to move primary to ensure the proper shard id is selected.
- is related to
-
SERVER-86593 MoveCollection hangs if the destination shard is specified as the shard url
- Closed