[SERVER-27110] clear OplogBuffer at the end of initial sync Created: 18/Nov/16 Updated: 05/Apr/17 Resolved: 21/Nov/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.1, 3.5.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Backport Completed: | |
| Sprint: | Repl 2016-11-21 |
| Participants: |
| Description |
|
We clear the OplogBuffer in _resetState_inlock: https://github.com/mongodb/mongo/blob/8c5d01498d1dfa8eef4292db4d32e6e6465a1580/src/mongo/db/repl/data_replicator.cpp#L352 When the call to this function got moved from the end of initial sync to the beginning, we no longer cleared the OplogBuffer at the end of initial sync. |
| Comments |
| Comment by Githook User [ 01/Dec/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: (cherry picked from commit 56ca0997552b466fa4b263c5a2105075df306a7a) |
| Comment by Githook User [ 21/Nov/16 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |