-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-02-17, CAR Team 2025-03-03, CAR Team 2025-03-17
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When upgrading to the next major FCV, the shards will become authoritative. In order to be so, they need to have persisted the authoritative database metadata in the replicated collection `config.shard.databases` and the DSS filled.
This ticket aims to introduce the first piece of this transition, by introducing a DDL that clones the global catalog to the shard-local catalog and cache (DSS) for a specific database. This DDL will be run in the primary shard and will serialize by other DDLs by taking the DDL lock.
- is depended on by
-
SERVER-101884 Consider removing clone_authoritative_db_metadata.js test
-
- Closed
-
- related to
-
SERVER-101625 Make DDLs clone database metadata from a single database of the global catalog to shard catalog if they are in kUpgrading FCV
-
- Closed
-