[DOCS-10937] Add Oplog Size and Initial Sync relation to 3.2 replica set documentation Created: 24/Oct/17 Updated: 30/Oct/23 Resolved: 27/Oct/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Renato Riccio | Assignee: | Anthony Sansone (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | initialSync, replica-set, v3.2.1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
https://docs.mongodb.com/v3.2/core/replica-set-sync/#initial-sync |
||
| Participants: | |
| Days since reply: | 6 years, 14 weeks, 5 days ago |
| Story Points: | 0.3 |
| Description |
|
Until 3.2, in order to have a successful sync between primary and secondary, the initial sync has to last less than the oplog window. In 3.4 this is not anymore strictly necessary since the secondary streams the oplog at the same time it performs the inital sync. The 3.2 constraint on the oplog size is not reported in the documentation, maybe it could be added here: |
| Comments |
| Comment by Githook User [ 03/Nov/17 ] |
|
Author: {'name': 'Anthony Sansone', 'username': 'atsansone', 'email': 'tony.sansone@mongodb.com'}Message: ( Signed-off-by: kay <kay.kim@10gen.com> |