-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
The config.placementHistory collection contains metadata on past cluster events (points in time) that may be incorrect/have no significance when directly copied from a backup archive - and there is no easy logic to patch them. Consistent content may be instead regenerated by running resetPlacementHistory once the rest of the config catalog has been restored.
- is related to
-
SERVER-93221 Drop config.placementHistory metadata in magic restore
- Needs Merge
-
SERVER-81137 Add feature flag to reset placement history on FCV upgrade
- Closed
- related to
-
SERVER-77416 ShardingCatalogClient should reject queries to config.placementHistory when no shard is registered in the Sharding Catalog
- Backlog