[SERVER-16234] clear oplog before starting initial sync Created: 19/Nov/14 Updated: 11/Jul/16 Resolved: 19/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Eric Milkie |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
If an initial sync encounters a problem any time after the first oplog sync phase, it can leave data behind in the oplog. When the node is restarted, another initial sync begins automatically, but the code isn't set up to work properly in the presence of data preexisting in the oplog. We need to clear out the old data before beginning a new initial sync. |
| Comments |
| Comment by Githook User [ 19/Nov/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |