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

Limit max number of keys to check

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

      We should consider adding a server parameter as limit on the max number of keys to check in a batch on secondaries (independent of batch boundaries), both for extra keys and missing keys checks. This is because if there are many inconsistent entries but we use minKey as the start of the first batch, or maxKey as the end of the last batch, those first/final batches may do a lot of work on the secondaries that the primary may not expect. As a result, this can slow down oplog application.

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            xuerui.fa@mongodb.com Xuerui Fa
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: