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

cap the default initial oplog size

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.5.1
    • Affects Version/s: 2.5.0
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

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

              Created:
              Updated:
              Resolved: