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

Process oplog inserts, and applying, on the secondary in parallel

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication, Storage
    • Fully Compatible
    • QuInt A (10/12/15)
    • 0

      Do not wait for the apply of the oplog entries before recording them in the oplog. This means both of these operation can be done concurrently instead of serially now that we record the boundaries of the batch and recover correctly but removing the oplog entries record during failures.

      old description
      Inserts into the oplog on the primary are done in parallel by each connection thread, whereas they are done on the secondary serially by the sync thread. This means that the oplog inserts are considerably slower on the secondary, which can create replication lag. See this comment for more information.

            Assignee:
            backlog-server-tuning [DO NOT USE] Backlog - Tuning Team
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            4 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated:
              Resolved: