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

Ensure oplog cannot be truncated due to capped deletions in standalone mode

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2018-09-10, Repl 2018-09-24, Repl 2019-02-25, Storage NYC 2019-03-25

      Description

      If the oldest oplog entries are truncated, replication recovery may not be able to succeed. We are recommending that backup services insert into the oplog as a standalone so replication can do its own recovery to a point-in-time, but this requires that the oplog can grow indefinitely.

        Attachments

          Issue Links

          is related to

          Task - A task that needs to be done. SERVER-36494 Prevent oplog truncation of oplog entries needed for startup recovery

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-39679 Add callback to replication when storage takes a checkpoint to learn of the maximum oplog truncation timestamp

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: