Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Won't Fix
Priority: Minor - P4
Fix Version/s: None
Affects Version/s: 3.0.0
Component/s: WiredTiger
Labels:
None

Operating System:
ALL
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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)

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

Assignee:: Unassigned
Reporter:: Chad Kreimendahl
Participants:: Chad Kreimendahl, Daniel Pasette, Johannes Richter, Michael Brenden, Michael Cahill, Ramon Fernandez Marina
Votes:: 1 Vote for this issue
Watchers:: 16 Start watching this issue

Created:: Mar 23 2015 08:01:56 PM UTC
Updated:: Jun 15 2020 05:18:22 PM UTC
Resolved:: Jul 01 2015 07:00:14 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates