The ShardingCatalogManager method supporting the initialization or reset of config.placementHistory is currently protected by an in-memory lock  ensuring that only a single attempt may be processed at a given time.

To ensure a consistent behavior, read requests coming through _configsvrGetHistoricalPlacementInfo should also acquire the same lock.