[DOCS-6376] as long as oplog window on any replica set members can span back to the snapshot’s timestamp, seeding a secondary will work Created: 15/Oct/15  Updated: 11/Jan/17  Resolved: 19/Nov/15

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Minor - P4
Reporter: Jun Wan Assignee: Bob Grabar
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:
Days since reply: 8 years, 18 weeks ago

 Description   

This is the current documentation about seeding a secondary

*https://docs.opsmanager.mongodb.com/current/tutorial/use-restore-to-seed-secondary/#considerations
*https://docs.cloud.mongodb.com/tutorial/use-restore-to-seed-secondary/#considerations

In these documentation, there is a paragraph as follows

"Seeding a new secondary from a backup restore requires an oplog window on the current primary that spans back to the snapshot’s timestamp."

It's not true. Seeding a new secondary does not require oplog window on current primary. As long as the oplog window of any replica set member is sufficient, seeding a new secondary will work.

Therefore, we advise to change it to

"Seeding a new secondary from a backup restore requires an oplog window on at least one replica set member that spans back to the snapshot’s timestamp."


Generated at Thu Feb 08 07:52:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.