[SERVER-33108] Collection deleted - file still exists Created: 03/Feb/18 Updated: 28/Feb/18 Resolved: 03/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrey Kostin | Assignee: | Kelsey Schubert |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
I have a replica set of 2 data nodes and 1 arbiter. On primary I ran two commands: The collections successfully deleted from primary and secondary but they still exist as files in collection directory. How to tell mongodb that they should be removed from disk? Don't want to keep 400Gb of useless data. |
| Comments |
| Comment by Kelsey Schubert [ 03/Feb/18 ] |
|
Hi lisio, Thanks for reporting this issue. In MongoDB 3.4.11 and later, this issue has been resolved by As a workaround, restarting the mongod will free the disk space. Kind regards, |