[DOCS-5809] Explain how delayed secondaries apply the oplogs Created: 09/Jul/15 Updated: 30/Oct/23 Resolved: 24/May/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Daniel Coupal | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 5 years, 38 weeks ago | ||||
| Description |
|
Could not find a place in the doc that describes how the delayed secondaries are applying oplogs.
The answer is 1. This page may be a good place to add the info: |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 24/May/18 ] |
|
The current Delayed Replica Set Members page describe this behaviour:
The "copy and apply" step requires the delayed secondary to have an oplog point in common with the source oplog. |