SERVER-136868ClosedFixed

resetPlacementHistory can leave config.placementHistory recreated without its secondary indexes by a concurrent DDL commit, crashing the config server on step-up (fassert 40184)

During resetPlacementHistory InitializePlacementHistoryCoordinator drops config.placementHistory in its kDefineInitializationTime phase, but only re-creates the collection and its two secondary indexes (nss_1_timestamp_-1 unique, timestamp_-1_nss_1) two phases later, in kComputeInitialization. In between, DDLs are unblocked: the kUnblockDDLs cluster-parameter broadcast takes effect per-shard as soon as each shard receives it, even while the phase handler itself is still running. A DDL that co

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.1.0-rc1025
Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.