[SERVER-60851] FileCopyBasedInitialSync moves from the wrong directory, misses a file Created: 20/Oct/21 Updated: 29/Oct/23 Resolved: 21/Oct/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: | Repl 2021-11-01 |
| Participants: |
| Description |
|
Since we run the file mover while storage is open in the dummy directory, we must pass the file mover the original dbpath, not the current one. Also we should delete "WiredTiger.lock"; this is as distinguished from "mongod.lock" which we should not touch (and shouldn't exist anyway). |
| Comments |
| Comment by Githook User [ 21/Oct/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |