Use wall instead of ts field for oplog retention policy

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • None
    • Fully Compatible
    • Execution Team 2020-02-24, Execution Team 2020-03-09
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As outcome of the scope / design discussion for this project, we decided to do the extra work to use the wall field instead of the ts field to calculate the age of oplog entries for retention purposes.

      This requires a new wall member in the OplogStones::Stone struct, as well as code to set it properly during oplog scanning/sampling at startup as well as steady state oplog stone creation.

            Assignee:
            Andrew Chen
            Reporter:
            Geert Bosch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: