[SERVER-61536] Treat WiredTiger journal directory specially in File Copy Based Initial Sync Created: 16/Nov/21  Updated: 16/Nov/21  Resolved: 16/Nov/21

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Matthew Russotto
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-61537 Delete WiredTigerPreplog and WiredTig... Closed
Operating System: ALL
Sprint: Replication 2021-11-29
Participants:

 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.


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