Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-51095

Keep track of OpCtxs created by PrimaryOnlyService threads and interrupt them at stepdown

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.8.0
    • 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.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: