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

Improve the way we are handling secondaryDelaySecs in OplogWriter

    • Replication
    • Fully Compatible
    • Repl 2024-02-19

      Currently, the writer batcher check the last entry in the batch and wait that entry to meet secondaryDelaySecs before we return the batch. This could cause some unexpected delay when the timespan in one batch is large, though this will only happen for one batch. Also, when the batcher is interrupted, we can return a batch that is not meeting the secondaryDelaySecs requirement.

      We can make the batcher smarter to break a batch and only return the batches satisfying secondaryDelaySecs.

      Since two problems are minor, we decided to track it in a separate Improvement ticket.

            Assignee:
            jiawei.yang@mongodb.com Jiawei Yang
            Reporter:
            jiawei.yang@mongodb.com Jiawei Yang
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: