[SERVER-62631] Implement the abort logic during a failure where the backup is imported into the server in the first phase Created: 13/Jan/22  Updated: 06/Dec/22  Resolved: 24/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Backlog - Storage Execution Team
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-62629 Create a new internal command that al... Closed
depends on SERVER-62630 Implement the first phase of the rest... Closed
depends on SERVER-62633 Implement the first phase of the rest... Closed
depends on SERVER-62634 Implement the final steps of the firs... Closed
Assigned Teams:
Storage Execution
Participants:

 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.


Generated at Thu Feb 08 05:55:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.