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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8.0
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Service arch 2020-10-05

      Description

      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.

        Attachments

          Activity

            People

            Assignee:
            spencer Spencer Brody (Inactive)
            Reporter:
            spencer Spencer Brody (Inactive)
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: