Clarify exclusive/inclusive mayTruncateUpTo bound for oplog truncation

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Storage Execution 2026-07-06, Storage Execution 2026-07-20, Storage Execution 2026-08-03
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This comment for reclaimOplog states that mayTruncateUpTo is an inclusive upper bound. However, from the implementation of checkOplogTruncationBounds, it is actually an exclusive upper bound.

      This API should be clarified and updated, with unit tests proving that it is an exclusive upper bound.

            Assignee:
            Unassigned
            Reporter:
            Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: