[SERVER-22985] Allow dropDatabase to accept flags to delete underlying directory Created: 07/Mar/16 Updated: 06/Dec/22 Resolved: 15/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Usability |
| Affects Version/s: | 3.3.2 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Chad Kreimendahl | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Do | Votes: | 8 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Description |
|
For those of us who create many temporary databases that get deleted, the new functionality that leaves database directories intact (even when they're not mount points or symlinks), can cause problems of managing the server. Please add in a flag or set of options (json?) to allow us to tell dropDatabase to delete the directory upon completion. This would act the exact same way that MMAP does today. Additionally, you could provide the option to delete "only if not symlink or mount point" or any combination of those options. Related to: |
| Comments |
| Comment by Chad Kreimendahl [ 21/Oct/19 ] |
|
It would be possible to check if it's a mount point or at least allow the user to "TRY" vs "FORCE" |
| Comment by Sherry Ummen [ 01/Aug/18 ] |
|
After 1 year, I am still requesting this. Please fix this. |
| Comment by Sherry Ummen [ 11/Jan/17 ] |
|
this would be nice to have. please |
| Comment by Bruce Lucas (Inactive) [ 07/Mar/16 ] |
|
Note that it's not actually even possible to remove the directory under Linux if it's a currently mounted mount point - it will fail with EBUSY. |