Separate eligible and ineligible oplog entries for the applier with secondaryDelaySecs

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Fully Compatible
    • v8.1, v8.0, v7.0
    • Repl 2025-06-09
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      It's possible for oplog entries on both sides of now - secondaryDelaySecs to land in the same oplog buffer batch. This prevents all oplog entries in that batch from being applied, so replication stops.

            Assignee:
            Evelyn Wu
            Reporter:
            Brad Cater
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: