[SERVER-19775] Do not apply the first oplog entry during initial sync Created: 05/Aug/15 Updated: 21/Sep/15 Resolved: 07/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.5, 3.1.6 |
| Fix Version/s: | 3.1.7 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | RPL 7 08/10/15 | ||||||||
| Participants: | |||||||||
| Description |
|
Since the data copy happens after the first oplog entry used to initialize the local oplog during initial sync there is no need to apply it. |
| Comments |
| Comment by Githook User [ 07/Aug/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |