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

Allow pipelining of applier work before updating-position/reporting

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.0-rc2
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl C (11/20/15)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the applier must (sequentially) do the following in a loop:

      1. batch oplog entries
      2. apply and record in local oplog
      3. journal, including minvalid
      4. report/update-position

      The task here is to break the last two steps (journal + reporting) into a separate process which doesn't block the next batch from starting/applying. This should allow higher throughput on the replicas without adversely affecting latency.

            Assignee:
            matt.dannenberg Matt Dannenberg (Inactive)
            Reporter:
            scotthernandez Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: