Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-61048

Make BackupCursorService use current engine instead of storing a stale one

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2021-11-01, Replication 2021-11-15

      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();

            Assignee:
            m.maher@mongodb.com Moustafa Maher
            Reporter:
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: