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

Cache the pointer to the oplog collection before running recoverToOplogTimestamp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker - P1
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.4.2
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-11-16

      Description

      For recoverFromOplogAsStandalone, we haveĀ this to set up the oplog collection pointer correctly before running any replication recovery. And this is needed since SERVER-45626 to use the AutoGetOplog helper.

      But we are missing the acquireOplogCollectionForLogging call in recoverFromOplogUpTo. Additionally, the oplog name in LocalOplogInfo is not set up correctly read-only mode with recoverToOplogTimestamp (it only considers the recoverFromOplogAsStandalone case).

      Last but not least, we dont seem to have any integration test coverages for running the server in readOnly mode with the recoverToOplogTimestamp server parameter.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              lingzhi.deng Lingzhi Deng
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: