[SERVER-5340] Add option to drop collection to remove empty db files, after drop Created: 19/Mar/12 Updated: 06/Dec/22 Resolved: 19/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
Add option, or just make it so, if the extents removed result in db files which have no extents then they can deleted to free disk space immediately. This would require a function which would be able to report any namespaces in a given db.X file to check if there are any left after the extent has been removed. We should make sure to always leave the require pre-allocated db file instead of deleting all empty db files. |