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

Do not truncate the last applied oplog entry during batch recovery

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.3.2
    • Affects Version/s: 3.2.0, 3.3.1
    • Component/s: Replication
    • None
    • Fully Compatible
    • v3.2

      Make the truncation of the oplog non-inclusive with minvalid.start (last applied oplog entry).

            Assignee:
            siyuan.zhou@mongodb.com Siyuan Zhou
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: