[DOCS-11484] Document that oplog size setting is now a soft limit Created: 23/Mar/18  Updated: 29/Oct/23  Due: 04/May/18  Resolved: 31/Jul/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: docs-grab-0504
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-29213 Have KVWiredTigerEngine implement Sto... Closed
Participants:
Days since reply: 5 years, 28 weeks, 1 day ago
Epic Link: DOCS: 4.0 Server

 Description   

Starting in 4.0, if the replication majority commit point lags past where the oplog would normally truncate, instead the oplog will grow to avoid deleting the majority commit point*. This means that the oplog size configuration is now a minimum size for the oplog, not a maximum. If writes are coming in but the majority point isn't moving (for example if secondaries aren't keeping up, or if you have a PSA set but the secondary is down), the oplog can grow past its configured size.

  • this growing behavior is actually related to the 'stable checkpoint timestamp', which is a pretty low level concept we probably don't want to expose to users, but it tracks the replication majority commit point pretty closely, so saying the replication commit point is probably close enough to accurate to get by.

Scope of changes:

  • mongod --oplogSize and replication.oplogSizeMB
  • source/administration/monitoring.txt
  • source/administration/production-checklist-operations.txt
  • source/core/capped-collections.txt
  • source/core/replica-set-delayed-member.txt
  • source/core/replica-set-oplog.txt
  • source/reference/command/replSetResizeOplog.txt
  • source/reference/command/serverStatus.txt
  • source/reference/limits.txt
  • source/reference/local-database.txt
  • source/reference/method/db.getReplicationInfo.txt
  • source/tutorial/change-oplog-size.txt
  • source/tutorial/configure-a-delayed-replica-set-member.txt
  • source/tutorial/deploy-replica-set-for-testing.txt
  • source/tutorial/expand-replica-set.txt
  • source/tutorial/resync-replica-set-member.txt
  • source/tutorial/troubleshoot-replica-sets.txt
  • source/tutorial/troubleshoot-sharded-clusters.txt

 

Impact to other docs outside of this product:

MVP:

Resources:



 Comments   
Comment by Githook User [ 31/Jul/18 ]

Author:

{'name': 'kay', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-11484: oplog size can grow past max size
Branch: master
https://github.com/mongodb/docs/commit/99a2f2c71a51d978531bd694b2b6e8a05b6e0a08

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