[SERVER-9876] cap the default initial oplog size Created: 07/Jun/13  Updated: 27/Oct/23  Resolved: 18/Jun/13

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.5.0
Fix Version/s: 2.5.1

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-9818 Problems when starting MongoDB with >... Closed
Related
related to SERVER-82527 Complete TODO listed in SERVER-9876 Blocked
related to SERVER-56554 Complete TODO listed in SERVER-9876 Closed
is related to DOCS-3122 document new limit in auto-created op... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

We choose 5% of free disk space for the oplog if not specified with --oplogSize. This is not a good idea if you have a very large disk, as it will create such a large oplog that the local database will consume 100's of files. This might then push the listening sockets past 1024 and fall out of range for select() to work, and mongod will thus fail to start.



 Comments   
Comment by auto [ 18/Jun/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-9876 place upper limit on the default oplog size cont
Branch: master
https://github.com/mongodb/mongo/commit/cb50688cbb996615c03a09cb101888455eff42f7

Comment by auto [ 18/Jun/13 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-9876 place upper limit on the default oplog size
Branch: master
https://github.com/mongodb/mongo/commit/bfc57a632cf01135d271e460fbb07f4bbfceae9a

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