Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-9876

cap the default initial oplog size

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 2.5.0
    • 2.5.1
    • Replication
    • 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

          Activity

            People

              matt.dannenberg Matt Dannenberg
              milkie@mongodb.com Eric Milkie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: