[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: |