FileCopyBasedInitialSync moves from the wrong directory, misses a file

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

      Since we run the file mover while storage is open in the dummy directory, we must pass the file mover the original dbpath, not the current one.

      Also we should delete "WiredTiger.lock"; this is as distinguished from "mongod.lock" which we should not touch (and shouldn't exist anyway).

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

              Created:
              Updated:
              Resolved: