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

Start changeStreams at the lastAppliedOpTime not the lastCommittedOpTime

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.5.13
    • Replication
    • None
    • Fully Compatible
    • Repl 2017-09-11

    Description

      The last committed optime can be behind last applied, so if you pick that as the start time your stream might pick up writes that were done before the stream was established (if the writes were done without write concern)

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: