[SERVER-16116] Server should not start if datafiles from other storage engine are present in dbpath Created: 12/Nov/14  Updated: 13/Nov/14  Resolved: 12/Nov/14

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

Type: Improvement Priority: Minor - P4
Reporter: Adam Midvidy Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-15986 Starting with different storage engin... Closed
Related
related to SERVER-16082 Server should not startup if other st... Closed
Participants:

 Description   

Say I start mongod with mmapv1 enabled in a clean directory:

mongod --dbpath=mongodata --storageEngine=mmapv1

Then exit the server.

then if I start the server with the same dbpath but with wiredtiger:

mongod --dbpath=mongodata --storageEngine=wiredtiger

the server will happily start writing data files to the same directory mmapv1 was using. (Also happens if I do wiredtiger, than mmap)

This is probably going to cause some confusion and/or misconfiguration at some point. I think it would be better if we detected that we are starting in a non-empty dbpath with incompatible data files and refuse to start.


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