[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
https://docs.mongodb.com/v3.2/core/replica-set-oplog/


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: (DOCS-10937): Added Java Driver 3.5 compatibility.

Signed-off-by: kay <kay.kim@10gen.com>
Branch: master
https://github.com/mongodb/docs-ecosystem/commit/b999b4b43c88ff9361639a91baa16797dacdf740

Generated at Thu Feb 08 08:01:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.