Allow system threads to survive InterruptedDueToStorageChange

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.1.1
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Repl 2021-10-18, Repl 2021-11-01, Replication 2021-11-15, Replication 2021-11-29
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we switch out the storage engine at the end of File Based Initial Sync, all opCtxs will be interrupted with InterruptedDueToStorageChange. There should be no user opCtxs (and if there are, it is OK to interrupt them), but there will also be system opCtxs such as FTDC and the watchdog thread. This ticket has two parts

      1) Determine which system opCtxs exist at the end of initial sync

      2) Ensure the associated tasks can survive by creating a new opCtx

              Assignee:
              Adi Zaimi
              Reporter:
              Matthew Russotto
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: