[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.
1 - BackupCursorHooks::initialize(serviceContext, storageEngine);
2- initializer registration
3- BackupCursorService construction

hence BackupCursorService fails while trying to use it to open backupCursor:
_storageEngine->getLastStableRecoveryTimestamp();



 Comments   
Comment by Githook User [ 02/Nov/21 ]

Author:

{'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}

Message: SERVER-61048 Make BackupCursorService use current engine instead of storing a stale one
Branch: master
https://github.com/mongodb/mongo/commit/5218ed8e510bdc1a6bfc14084f81bcc236b90964

Comment by Githook User [ 02/Nov/21 ]

Author:

{'name': 'Moustafa Maher Khalil', 'email': 'm.maher@mongodb.com', 'username': 'moustafamaher'}

Message: SERVER-61048 Make BackupCursorService use current engine instead of storing a stale one
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/8029f01137ffe2dce5bed8b8aacb80594193de51

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