[SERVER-16080] Server should not fassert on invalid wiredtiger config options Created: 11/Nov/14  Updated: 11/Jul/16  Resolved: 13/Nov/14

Status: Closed
Project: Core Server
Component/s: Storage, Usability
Affects Version/s: None
Fix Version/s: 2.8.0-rc1

Type: Improvement Priority: Major - P3
Reporter: Adam Midvidy Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-16174 Assertion and backtrace when invalid ... Closed
Participants:

 Description   

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...



 Comments   
Comment by Githook User [ 13/Nov/14 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-16080 improve startup handling on invalid wiredtiger config options
clean up initialization of local.startup_log
Branch: master
https://github.com/mongodb/mongo/commit/0822fa2908d02d7154c9a1378526dbca97238608

Generated at Thu Feb 08 03:39:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.