[SERVER-61048] Make BackupCursorService use current engine instead of storing a stale one Created: 27/Oct/21 Updated: 29/Oct/23 Resolved: 02/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Moustafa Maher |
| 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, Replication 2021-11-15 |
| Participants: |
| Description |
|
BackupCursorHooks send a copy of the storageEngine pointer on startup, construct BackupCursorService with it, which will be invalidated after FCBIS. hence BackupCursorService fails while trying to use it to open backupCursor: |
| Comments |
| Comment by Githook User [ 02/Nov/21 ] |
|
Author: {'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: |
| Comment by Githook User [ 02/Nov/21 ] |
|
Author: {'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}Message: |