-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 7.3.0-rc0, 8.0.0-rc0
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
-
3
The shard where DDL operations run for the config database is the first shard in alphabetical order. This shard may change if a shard is added with a lower alphabetical value than the lowest one. We are assuming in most places that the collection exists on the shard where we run the DDL operations, which may not be the case for the config database.
We should find a way to keep this shard constant.
- is caused by
-
SERVER-52779 Implement the new create/shard collection path in `_shardsvrShardCollection`
- Closed
- is related to
-
SERVER-83924 system.session is not found locally when created as unsplittable
- Closed