[SERVER-30655] about oplog 50G Maximum value! Created: 15/Aug/17  Updated: 15/Aug/17  Resolved: 15/Aug/17

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: hiller1 Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File 1.png     PNG File 2.png    
Participants:

 Description   

mongodb - 3.2.11



 Comments   
Comment by Stennie Steneker (Inactive) [ 15/Aug/17 ]

Hi,

The documentation is correct as it is referring to the upper and lower bounds for the default oplog sizes that will be created based on free disk space. You can specify a larger oplog size than the default if this is more appropriate for your use case (see: Workloads that Might Require a Larger Oplog Size).

Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag.

Regards,
Stephen

Comment by hiller1 [ 15/Aug/17 ]

https://docs.mongodb.com/v3.2/core/replica-set-oplog/

Storage Engine Default Oplog Size Lower Bound Upper Bound
In-Memory Storage Engine 5% of physical memory 50 MB 50 GB
WiredTiger Storage Engine 5% of free disk space 990 MB 50 GB
MMAPv1 Storage Engine 5% of free disk space 990 MB 50 GB

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