-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Fully Compatible
-
Service arch 2020-10-05
Currently there is a small race condition where PrimaryOnlyService opCtxs can miss getting interrupted during stepdown. This can happen if a PrimaryOnlyService thread creates a new opCtx after the stepdown thread has already killed all OpCtxs as part of acquiring the RSTL lock, but before PrimaryOnlyService::onStepdown has been called.
Explicitly interrupting all OpCtxs owned by PrimaryOnlyServices in PrimaryOnlyService::onStepdown closes that window.