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

Improve pre-image truncate marker generation observability

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc9
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • v8.0
    • Execution Team 2024-05-13, Execution Team 2024-05-27, Execution Team 2024-06-10

      We currently log the "ns" of the pre-images collection truncate markers are generated for.

      It would be useful to have the UUID of the collection, to make sure it wasn't dropped and recreated from underneath.

      Some other ideas:

      • Log once the markers are installed & finalized
        • It's crucial to understand whether markers were installed, or whether they are going to be generated on the next removal pass. 
        • If markers are installed, but interrupted before they are finalized, truncation could be blocked since the highest seen RecordId isn't viewed. 

            Assignee:
            haley.connelly@mongodb.com Haley Connelly
            Reporter:
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: