Make _logOplogEntriesForInvalidResults resilient to non-existing oplog

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0, 5.0.22, 7.0.3, 6.0.12
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • v7.1, v7.0, v6.0, v5.0
    • Execution NAMR Team 2023-09-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      _logOplogEntriesForInvalidResults does not check if the oplog pointer is valid.

      One case where this could happen was when running validate on a replica set member started as standalone. Even though the oplog existed, AutoGetOplog returned nullptr. This is being handled in SERVER-80789.

      The other possibility is that the oplog doesn't actually exist because the node has always been standalone. We should check if it is possible to hit this code with timestamps in recordTimestamps (passing this check) in this case, and if so make the code resilient.

              Assignee:
              Benety Goh
              Reporter:
              Yujin Kang Park
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: