Include Flag in dropDatabase to delete empty database directory

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.6.14, 4.0.13, 3.4.23, 4.2.1, 4.3.1
    • Component/s: Storage
    • None
    • Server Triage
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we moved to wiredTiger, we ended up with a bunch of zombie directories. This was related to the desire not to delete those directories when the database that related to them was dropped.  

      If we could get an optional flag to send the dropDatabase command to tell it under which scenarios we want it to do the drops, that would reduce a bit of the risk of doing it the alternative way.

      SERVER-17703 has this recommendation on the current final comment.

       

      Deleting with a find -type d -empty in the data directory might work, but is less preferable than just asking dropDatabase to do it... especially when we know, as we do in our case, that it's entirely safe to delete any directory for a dropped database.

              Assignee:
              [HELP ONLY] Backlog - Triage Team
              Reporter:
              Chad Kreimendahl
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: