-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Catalog and Routing
-
CAR Team 2026-08-17
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Currently, checkMetadataConsistency only checks the shard catalog database info on the dbPrimary shard, but does not check the rest of the shards. Other shortcomings are that it only checks it when the autoritativeShards feature is on, and that it incorrectly short circuits when the database metadata is not found on a dbPrimary shard.
Proposal:
- Check on all shards
- On dbPrimary shard, when authoritativeShard=enabled, then the DSS and its backing collection must know that this shard is indeed the dbPrimary.
- On the non-dbPrimary shards, the DSS and its backing collections must not believe that this is the dbPrimary shard.
- is related to
-
-
- In Progress
-
- related to
-
SERVER-133194 dropDatabase can leave stale database metadata in the shard catalog during FCV upgrade
-
- Closed
-
-
-
- In Code Review
-