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

Start changeStreams at the lastAppliedOpTime not the lastCommittedOpTime

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.13
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2017-09-11

      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)

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

              Created:
              Updated:
              Resolved: