[SERVER-44120] Include Flag in dropDatabase to delete empty database directory Created: 20/Oct/19 Updated: 06/Dec/22 Resolved: 21/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.6.14, 4.0.13, 3.4.23, 4.2.1, 4.3.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chad Kreimendahl | Assignee: | Backlog - Triage Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Server Triage
|
||||||||
| Participants: | |||||||||
| Description |
|
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.
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. |