Details
-
Bug
-
Resolution: Done
-
Major - P3
-
2.5.0
-
None
-
Fully Compatible
-
ALL
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.
Attachments
Issue Links
- is depended on by
-
SERVER-9818 Problems when starting MongoDB with > 1023 FDs
-
- Closed
-
- is related to
-
DOCS-3122 document new limit in auto-created oplog sizes
-
- Closed
-
- related to
-
SERVER-56554 Complete TODO listed in SERVER-9876
-
- Closed
-
-
SERVER-82527 Complete TODO listed in SERVER-9876
-
- Needs Scheduling
-