Currenty we just log a warning. I'd argue that we should just return an error and shutdown.
amidvidy ~/Documents/gitroot/mongo $ ./mongod --wiredTigerCollectionConfig="bad=foo" --storageEngine=mmapv1 Collection option: bad=foo 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] MongoDB starting : pid=27307 port=27017 dbpath=/data/db 64-bit host=vader 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] ** NOTE: This is a development version (2.7.9-pre-) of MongoDB. 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] ** Not recommended for production. 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] db version v2.7.9-pre- 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] git version: 0549652e913b4c39dc00ec10bd1895c085b27bf3 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] build info: Linux vader 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] allocator: tcmalloc 2014-11-11T11:40:13.187-0500 I CONTROL [initandlisten] options: { storage: { engine: "mmapv1", wiredtiger: { collectionConfig: "bad=foo" } } } 2014-11-11T11:40:13.187-0500 W STORAGE [initandlisten] Detected configuration for non-active storage engine wiredtiger when current storage engine is mmapv1
- is documented by
-
DOCS-8990 Server should not startup if other storage engine options are used
-
- Closed
-
- is related to
-
SERVER-16116 Server should not start if datafiles from other storage engine are present in dbpath
-
- Closed
-
- related to
-
SERVER-16083 Creating collections should error with invalid storage options
-
- Closed
-