Correctly account for applyOps in oplog application batch size counting

XMLWordPrintableJSON

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

      applyOps commands are mixed in with other CRUD ops in oplog application batches, but we only count them as 1 operation towards the maximum allowed batch size. We should instead count them as the number of operations in the applyOps since that is a more realistic estimate of the amount of cache required for applying them.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: