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

Don't reserve oplog entries beyond those which will be used.

    • Replication
    • Fully Compatible
    • ALL
    • v8.0
    • Repl 2024-04-15, Repl 2024-04-29
    • 47

      Currently, when building an applyOps, we reserve as many optimes as we have operations to put into the applyOps, and then use the first N (for as many applyOps as we have). This is legal, but it advances the cluster time to the end of the reserved opTimes. This means that if we immediately follow doing an applyOps write with a causal secondary read, we will think the cluster time on the secondary is not up to date.

      We should either use the last N slots for the applyOps, or reserve the exact number of slots.

            Assignee:
            matthew.russotto@mongodb.com Matthew Russotto
            Reporter:
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: