[DOCS-961] Update/create documentation for "priming the oplog" to include setting minValid Created: 08/Jan/13  Updated: 30/Oct/23  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Major - P3
Reporter: Ian Daniel Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-7652 Initial sync criteria needs to check ... Closed
is depended on by SERVER-8139 New replication dep. on minvalid coll... Closed
Participants:
Days since reply: 11 years, 6 weeks, 1 day ago

 Description   

SERVER-7652 describes a change going into 2.2.3 in which initial sync criteria check minValid, not the oplog.

In cases in which we need to manually "prime the oplog" by inserting a document into a new oplog, e.g. when provisioning a secondary from a 'mongodump --oplog' and then 'mongorestore --oplogReplay' (SERVER-6080 gives a very brief overview), we now also need to set minValid. If minValid is not set, all data will be dropped and an initial sync done.

I cannot find anything on provisioning a secondary via mongodump/mongorestore in our official documentation. I am not sure if this is a deliberate choice or an omission. Given the impact of not setting minValid, we should consider documenting this procedure, including of course the need for the minValid.

By the way, manually setting of minValid is not needed when we change the size of the oplog, and as such that documentation does not need updating. (Tested on 2.3.2.)


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