[SERVER-16906] storage engines without directoryperdb support should fail to start up with --directoryperdb Created: 16/Jan/15  Updated: 23/Jan/15  Resolved: 16/Jan/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc5
Fix Version/s: 3.0.0-rc6

Type: Bug Priority: Minor - P4
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-16132 implement directoryperdb under WiredT... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

When starting up a server with a storage engine that does not provide --directoryperdb support (eg. rocksExperiment, devnull, ...), the storage engine silently ignores --directoryperdb and does not adopt a different layout for the data directory.

To reproduce, build mongod with --rocks and run the follow JS Test:

buildscripts/smoke.py --storageEngine=devnull jstests/noPassthrough/directoryperdb.js



 Comments   
Comment by Githook User [ 16/Jan/15 ]

Author:

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

Message: SERVER-16906 storage engines without directoryperdb support should fail to start up with --directoryperdb
Branch: master
https://github.com/mongodb/mongo/commit/020cc851f48cca51ba2ac6c94ca93119a4563c4f

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