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

Preimage truncate marker refresh does not drop concurrently inserted docs

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2024-05-27, Execution Team 2024-06-10, Execution Team 2024-07-22, Execution Team 2024-08-05, Execution Team 2024-08-19, Execution Team 2024-09-16, Execution Team 2024-09-30, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-11-11, Execution Team 2024-11-25
    • 200

      The marker initialisation code creates and installs markers, and then refreshes the markers to account for concurrent inserts. This refresh samples the last RecordId, and updates the highest wall time and RecordId, but does so without modifying byte and record count (code ref).

      Partial marker expiration depends on either record count or byte count being greater than 0 (ref).
      This means that any entry accounted for in the refresh will not be dropped even if the wall time and RecordId are correct (in the absence of new inserts).

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            yujin.kang@mongodb.com Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: