-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 9.0.0-rc0, 9.1.0-rc0
-
Component/s: None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-08-03, CAR Team 2026-08-17, CAR Team 2026-08-31
-
🟥 DDL
-
None
-
None
-
None
-
None
-
None
-
None
Currently CheckMetadataConsistency only checks CollectionShardingState entries of namespaces reachable through either the global or the local collection catalogs; other entries are never checked. Therefore we are missing validation that no stale CSS/DSS entries are left.
For example, after dropping a collection, we are missing validation that there are no CSS entries stating that collection exists.
- is duplicated by
-
SERVER-132479 Extend checkMetadataConsistency to detect CSR states without a matching durable entry
-
- Closed
-
- is related to
-
SERVER-133108 Improve CheckMetadataConsistency to also check metadata for non-existing databases
-
- In Code Review
-
-
SERVER-132479 Extend checkMetadataConsistency to detect CSR states without a matching durable entry
-
- Closed
-
-
SERVER-133107 Improve DSS checking in checkMetadataConsistency
-
- Closed
-
- related to
-
SERVER-133296 Investigate why CheckMetadataConsistency should not swallow UNTRACKED CSS for timeseries buckets collections
-
- Closed
-