-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Sharding, Upgrade/Downgrade
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2026-07-20
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Since SERVER-127979 we drop the legacy collections (config.cache.catalog.*) when upgrading.
Add testing / checkMetadataConsistency new checks to ensure those collections do not exist in a 9.0 FCV cluster.
- depends on
-
SERVER-96888 Enable feature flag featureFlagSymmetricFCV
-
- Closed
-
-
SERVER-119485 Add a persisted phase to setFCV after enabling target FCV features
-
- Closed
-
-
SERVER-127653 [Placeholder] All DDLs are authoritative
-
- Closed
-
-
SERVER-127979 Drop legacy shard catalog collections when upgrading
-
- Closed
-
- is related to
-
SERVER-127977 checkMetadataConsistency tests the authoritative shard catalog collections do not exist when downgraded
-
- Closed
-
- related to
-
SERVER-130709 CheckMetadataConsistency may flag a AuthoritativeShardCatalogCollectionsPresent false positive with concurrent setFCV
-
- Closed
-
-
SERVER-130949 Remove assert_no_legacy_shard_cache_collections.js test hook
-
- Closed
-