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

lastDurable optime should be updated after batch application on non-durable storage engines

    XMLWordPrintable

Details

    • Bug
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Replication
    • ALL
    • Repl 2018-07-30, Repl 2018-08-13, Repl 2018-08-27, Repl 2018-09-10
    • 17

    Description

      For secondary batch application, the ApplyBatchFinalizer is used to advance optimes after application of an oplog batch completes. We currently use the ApplyBatchFinalizerForJournal for durable storage engines and the ApplyBatchFinalizer for non-durable storage engines, which only updates the lastApplied optime. On primaries, for non-durable storage engines, the replication system keeps the lastDurable optime up to date wth the lastApplied optime, since the lastDurable optime has no functional meaning on a non-durable storage engine. It seems we should be keeping this behavior consistent between primaries and secondaries, so we should update the lastDurable optime on batch application on non-durable storage engines.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              william.schultz@mongodb.com William Schultz (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated: