[SERVER-9225] Oplog application during initial sync should be exclusive of the start/minValid oplog entry Created: 03/Apr/13 Updated: 10/Dec/14 Resolved: 03/Apr/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
At the beginning of initial sync, we take note of the current most recent document in the primary's oplog. After cloning the data, we apply the oplog for all entries newer than and including the entry that was noted to start with. We should only apply entries newer than the initial one. This can cause problems when users do complex backup/restore procedures where the document referred to by the most recent oplog entry ceased to exist because of modifications to the file system outside of MongoDB. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 03/Apr/13 ] |
|
the oplog is designed to be idempotent, so any backup procedure that requires that level of knowledge is not going to be reliable over the course of time. |