Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-17703

dropDatabase not removing folders with wiredTiger

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Won't Fix
    • Affects Version/s: 3.0.0
    • Fix Version/s: None
    • Component/s: WiredTiger
    • Labels:
      None
    • Operating System:
      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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-1379 dropdb with directoryperdb should remove contents, not delete directory (mmapV1)

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-22985 Allow dropDatabase to accept flags to delete underlying directory

          • Major - P3 - Major loss of function.
          • Open

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: