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

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication, Storage
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      QuInt A (10/12/15)
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-tuning Backlog - Tuning Team
              Reporter:
              bruce.lucas Bruce Lucas
              Participants:
              Votes:
              4 Vote for this issue
              Watchers:
              31 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: