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

Implement the abort logic during a failure where the backup is imported into the server in the first phase

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      There's a few cases to consider here.

      After moving the files from _restore into the dbpath, then an unclean shutdown during this point will leave files unowned by both mongod and WiredTiger. During startup recovery when aborting the restore procedure, these files need to be removed from the filesystem.

      Table imports in WiredTiger are non-transactional. An unclean shutdown during this procedure could result in some files owned by WiredTiger but not known to mongod. During startup recovery when aborting the restore procedure, some tables may need to be dropped through WiredTiger.

      Once the collections are imported in both the server and WiredTiger, the abort procedure will need to remove any durable catalog changes in the server as well as dropping tables in WiredTiger during startup recovery.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: