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

Server should not fassert on invalid wiredtiger config options

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.8.0-rc1
    • Affects Version/s: None
    • Component/s: Storage, Usability
    • None
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      Fasserting is a bit heavy handed for this IMO. We should have the same behavior for an invalid WT option as we do for other invalid options.

      Example: invalid (non-WT) option

      amidvidy ~/Documents/gitroot/mongo $ ./mongod --setParameter fakeParam=FOO
      BadValue Illegal --setParameter parameter: "fakeParam"
      try './mongod --help' for more information
      
      amidvidy ~/Documents/gitroot/mongo $ ./mongod --storageEngine=wiredtiger --wiredTigerCollectionConfig="bad=foo"
      ...
      2014-11-11T11:37:19.882-0500 I -        [initandlisten] Fatal assertion 28520 UnknownError 22: Invalid argument
      .. stacktrace...
      

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            adam.midvidy Adam Midvidy (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: