[SERVER-30847] Start changeStreams at the lastAppliedOpTime not the lastCommittedOpTime Created: 25/Aug/17  Updated: 30/Oct/23  Resolved: 28/Aug/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.5.13

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-09-11
Participants:

 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)



 Comments   
Comment by Githook User [ 25/Aug/17 ]

Author:

{'email': 'matthew.russotto@10gen.com', 'name': 'Matthew Russotto', 'username': 'mtrussotto'}

Message: SERVER-30847 Start changeStreams at the lastAppliedOpTime not the lastDurableOpTime
Branch: master
https://github.com/mongodb/mongo/commit/ec42f5f16ff7809c5b1ed29601978e9e98aa5925

Generated at Thu Feb 08 04:25:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.