SERVER-104325ClosedFixed

[v8.0] DDL lock acquisition can hang indefinitely on secondaries

The {{setAlwaysInterruptAtStepDownOrUp_UNSAFE()}} function on the operation context is unsafe in a sense that if a stepdown happens during the run of that function, the said stepdown (and the interruption) would be missed. If a component tries to acquire the DDL lock after it became a secondary, it will hang for 5 minutes (the default timeout for the DDL lock acquire) since the DDL lock acquisition waits for the recovery of the {{{}ShardingDDLCoordinator{}}}, what will never happen because th

Affected Versions
Versions known to exhibit this issue
7.0.08.0.0
Fixed Versions
Versions that include the fix
8.0.167.0.49
Components
Server components related to this issue

No components specified.

Labels
Tags and classification
v8.0