[SERVER-16175] allowing multiple storage engines in same dbpath creates opportunity for error Created: 16/Nov/14  Updated: 17/Nov/14  Resolved: 16/Nov/14

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 2.8.0-rc0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: wiredtiger
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-15986 Starting with different storage engin... Closed
Participants:

 Description   

Consider a scenario where a customer by mistake starts mongod with the wrong storage engine parameter in a production system. Under the current design mongod will start up and create an empty db in dbpath using that wrong storage engine. Queries to that mongod will begin to fail; it may also begin accepting data and putting it in the wrong db, creating a difficult situation to recover from. We could eliminate this possible source of error by refusing to start if the files currently in dbpath are for a storage engine different from the startup option.


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