[SERVER-34565] oplog reads on secondaries should read at lastApplied timestamp Created: 19/Apr/18 Updated: 29/Oct/23 Resolved: 20/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Storage NYC 2018-04-23 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 50 | ||||||||||||
| Description |
|
Currently, oplog reads use the oplog visiblity timestamp, but this value is not maintained properly while a batch is being applied. |
| Comments |
| Comment by Githook User [ 20/Apr/18 ] |
|
Author: {'email': 'milkie@10gen.com', 'username': 'milkie', 'name': 'Eric Milkie'}Message: |