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

Revisit allDurable and lastApplied check before truncation of pre-images

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution

      Right now, the allDurable and lastApplied timestamps are computed once, and used as a barrier to protect against truncating pre-images that are not yet part of a consistent range of data (due to oplog holes/ secondary oplog application).

      We should reconsider placing the check in _hasExcessMarkers so pre-images are not considered 'excess' from the start, rather than waiting to do the check before truncation.

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

              Created:
              Updated:
              Resolved: