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

Unify oplog visibility timestamp updates

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • Replication

    Description

      Now, both initial syncer and oplog applier rely on calling oplogDiskLocRegister to update oplog visibility ts after calling multiApply. After SERVER-42925, idempotency tests also rely on oplogDiskLocRegister to mimic the server behavior. This makes it very easy for one to forget calling oplogDiskLocRegister. It seems that it is always the case that we want to update oplog visibility after oplog application. So it is probably a good idea to unify/merge the oplog visibility logic into multiApply.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: