OplogTruncateMarkers don't preserve OplogStone legacy initialisation behavior

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2023-04-03
    • 20
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      There is a difference between OplogTruncateMarkers and legacy OplogStones on how to determine whether to sample or scan the existing oplog recordstore.

      Prior to SERVER-46870, the OplogStones (now renamed OplogTruncateMarkers) were computed via scanning based on "numStonesToKeep".

       

      Post SERVER-46870, scanning is performed pending a constraint that isn't equivalent unless dataSize were equivalent to the maxSize. 

            Assignee:
            Haley Connelly
            Reporter:
            Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: