Details
-
Bug
-
Resolution: Won't Fix
-
Minor - P4
-
None
-
3.0.0
-
None
-
ALL
Description
When doing a dropDatabase() using MMAPv1 on versions from 2.4 -> 3.0.1, the relevant folders which contain the data when using directoryPerDB: true are also removed.
However, when performing the same dropDatabase using the wiredTiger engine and directoryPerDB: true, the directories are left in-tact, and only the related files are removed.
(note, only tested with directoryForIndexes: true in 3.0.1)
Attachments
Issue Links
- is related to
-
SERVER-48882 If directoryperdb is active, remove empty directories
-
- Closed
-
-
SERVER-1379 dropdb with directoryperdb should remove contents, not delete directory (mmapV1)
-
- Closed
-
- related to
-
SERVER-22985 Allow dropDatabase to accept flags to delete underlying directory
-
- Closed
-