[DOCS-13830] [SERVER] Define the "oplog replication window" Created: 13/Aug/20  Updated: 30/Oct/23  Resolved: 24/Aug/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.2.0, 4.4.0, 5.0.0, 6.0.0
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Nic Cottrell Assignee: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 0
Labels: docs-server-onboarding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-15459 Create "Known Issue" docs for ChangeS... Closed
Participants:
Days since reply: 1 year, 22 weeks, 1 day ago
Epic Link: DOCSP-11702

 Description   

Description

Neither the Oplog page nor the Glossary page define the "oplog replication window" clearly, but this is a term used in Atlas metrics etc.

I would like to see some text like:

"The oplog window is the time difference between the newest and the oldest timestamps in the oplog, and limits how far back in time an secondary node can catch up replication after being offline for maintenance or unscheduled downtime"/

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 06/Sep/22 ]

Author:

{'name': 'Dave Cuthbert', 'email': '69165704+davemungo@users.noreply.github.com', 'username': 'davemungo'}

Message: DOCS-13830 oplog definition (#1702)

Comment by Githook User [ 24/Aug/22 ]

Author:

{'name': 'Dave Cuthbert', 'email': '69165704+davemungo@users.noreply.github.com', 'username': 'davemungo'}

Message: DOCS-13830 BACKPORT (#1713)
Branch: v5.0
https://github.com/10gen/docs-mongodb-internal/commit/71876d856fa8ccd3bf7c0cf890fc7ac58165e5e6

Comment by Leah Coleman [ 23/Aug/22 ]

adam.harrison@mongodb.com nicholas.cottrell@mongodb.com We can get this into the KB pretty quickly, and can always archive it out later if it's officially added to docs (or do a redirect since we write KBAs for search context) The only caveat is that it won't be public as we don't yet have any articles configured for non-authentication, but it will at least be customer-facing. If that's OK, I will file a TSWRITING ticket and get this out this week since it's a small article.

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