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

Report maximum timestamp eligible for pre-image truncation in server status

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2024-08-19, Execution Team 2024-09-16, Execution Team 2024-09-30
    • 0

      Pre-image truncation occurs only if pre-images are older than the maximum timestamp eligible for truncation. This is to prevent truncation a pre-image range where pre-images can still be written. 

      Given the computation is the minimum of the lastApplied and allDurable, it would be useful to expose the timestamp, to know whether the system believes a pre-image is truncate eligible. 

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

              Created:
              Updated:
              Resolved: