As a preventive measure against potential data corruption, a new command should be made available to the user to trigger a re-initialisation of config.placementHistory based on the content of the rest of the sharding catalog (leveraging the logic introduced as part of SERVER-70687.
- depends on
-
SERVER-76406 Avoid querying previous config.placementHistory documents when inserting new ones
- Closed
- is duplicated by
-
SERVER-73816 Define process to migrate config.placementHistory as part of automated restores
- Closed
-
SERVER-75934 Check earliestOpTime is earlier than latest placementHistory validity marker opTime
- Closed