[SERVER-12707] resync command should clear lastOpTimeWritten in oplog.cpp Created: 12/Feb/14 Updated: 11/Jul/16 Resolved: 18/Feb/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | 2.6.0-rc0 |
| 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 |
| Steps To Reproduce: | Run the resync command and during initial sync you will see the "replication oplog stream went back in time." message in the server log, and it will redirect syncing back to the primary. |
| Participants: |
| Description |
|
Otherwise, logOp gets annoyed because it thinks we are logging the same op as last time, even though we have cleared out the oplog so it's a non-issue. |
| Comments |
| Comment by Githook User [ 18/Feb/14 ] |
|
Author: {u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}Message: |