[SERVER-5853] Decouple replication to oplog from application of oplog entries Created: 16/May/12 Updated: 09/Jul/16 Resolved: 22/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | oplog, replication | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Allow replication to replicate the oplog independent from the application of the oplog entries to databases. This would require the storage of the current oplog entry which replication should apply from being stored outside of the oplog. We will also need to allow some way to stop replaying replication on replicas: see linked issue |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 22/Mar/13 ] |