File Copy Based Initial Sync needs to keep opCtx, client, and thread coherent.

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2021-11-01
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We need to hold the global lock across scheduled calls in FileCopyBasedInitialSyncer. Our current method for doing this involves holding RAII objects (GlobalLock) in places other than the stack. GlobalLock holds an _opCtx, and _opCtx are associated with a particular client, which are typically associated with a particular thread. We need to use a different method to keep this lock held.

            Assignee:
            Matthew Russotto (Inactive)
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: