-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
ALL
Currently, when we add a replica set to a sharded cluster using the addShard command, and that replica set contains data, we manually register the collection in the global catalog by writing to config.databases.
In the context of SPM-3729, this process bypasses registration in the shard-local catalog, which makes the shards not being authoritative for databases.
- depends on
-
SERVER-100447 Temporary ban tests that add a replica set with existing dbs in a sharded cluster
- In Code Review
- related to
-
SERVER-80532 Sharding catalog may be missing databases created via direct connections during/after addShard
- Backlog