-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
CAR Team 2025-03-31
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Magic restore supports selective restore of collections. When performing such a restore in a sharded cluster, it will send a _configsvrRunRestore to the config server to remove metadata of non restored collections. Since now shards store metadata authoritatively, we need to send a similar command also to shards.
- depends on
-
SERVER-68747 Drop databases during a selective restore if no collections in the database were restored
-
- Backlog
-
- related to
-
SERVER-100083 Refine _configsvrRunRestore to Include Database Metadata Collections on Config Shards
-
- Closed
-
-
SERVER-99799 Consider adding `config.shard.databases` to the magic restore procedure
-
- Closed
-