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

Decouple oplog fetching from oplog application

    • Type: Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication

      Currently we don't fetch a new batch of oplog entries until we have finished applying the previous batch. Instead, we should fetch oplog entries as fast as we can get them from our sync source and write them down, and in parallel we should be applying oplog entries as fast as we can. This would be especially useful in conjunction with SERVER-32513, so that when coming out of initial sync you never stop syncing from your sync source, which would greatly limit the degree to which initial sync was dependent on the size of its sync source's oplog.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: