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

Add an easy way to take action on no-op oplog entries

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication

    Description

      We've started using no-op oplog entries as ways to convey internal information throughout the system - for example in change streams and as part of retriable writes. This usage is likely to increase with future transaction work. No-op oplog entries, however, do not currently have an OpObserver. We should add an easy way for secondaries (and maybe also primaries?) to listen for and take action on any no-op oplog entries, potentially by working them into the existing OpObserver system or potentially via a new mechanism

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: