[SERVER-61253] InitialSyncFileMover must handle symlinks at top level of destination directory Created: 04/Nov/21 Updated: 29/Oct/23 Resolved: 08/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Replication 2021-11-15 |
| Participants: |
| Description |
|
Currently, InitialSyncFileMover assumes all existing files are regular files or directories; if one is a symlink we get an invariant. We sometimes create a symlink to put the WiredTiger journal files on another device. This means we must support some of the files to delete containing a symlink at the top level of their path. We must preserve that symlink, so files with the same relative path from the sync source go into the symlink destination directory. |
| Comments |
| Comment by Githook User [ 08/Nov/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |