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

Separate secondary oplog application storage transactions with many index writes

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Replication

      If applying an oplog entry requires many index writes, it can cause write conflicts (due to cache pressure) and slowness, especially as the size of the storage transaction increases. There's no need to apply the entire oplog entry in one storage transaction (we currently split up prepared transactions into multiple storage transactions, for example). I'm not sure the best way to determine when to split up a storage transaction.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: