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

oplog default size must be differently calculated for inMemory storage engine

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 3.2.6, 3.3.5
    • Replication
    • Fully Compatible
    • ALL
    • Repl 13 (04/22/16)

    Description

      If oplog size is not specified, we calculate it using default based on free space on disk. This makes little sense for inMemory storage engine and will most likely never be the right size.

      We should either fail to start if oplog size is not specified explicitly for a replica set member on startup, or we should calculate a different default, based on memory size (like we do cache) not based on disk size (and maybe give a warning in the logs that the size was not specified).

      Attachments

        Issue Links

          Activity

            People

              milkie@mongodb.com Eric Milkie
              asya.kamsky@mongodb.com Asya Kamsky
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: