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

Treat WiredTiger journal directory specially in File Copy Based Initial Sync

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL
    • Replication 2021-11-29

    Description

      Normally we completely replace the WiredTiger 'journal' directory when doing a File Copy Based Initial Sync. If that directory is a symlink (as it is in our perf infrastructure) we instead copy and delete files within it. Because of some WiredTiger issues, we need to treat this directory in a special way. All files prefixed with WiredTigerLog must be deleted (even if they didn't appear in the backup cursor), since a new log file may have been created when we shut down. All files prefixed with WiredTigerPreplog or WiredTigerTmplog should not be moved from the .initialsync directory to the dbpath, as these files will be deleted by WiredTiger anyway. If we do move such a file, and a corresponding file already exists, we must delete it rather than rename it to a temporary name, because WiredTiger will fail with a fatal error if any files prefixed with a log prefix exist which do not match its naming scheme.

      Attachments

        Activity

          People

            matthew.russotto@mongodb.com Matthew Russotto
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: