[SERVER-42660] Compact not releasing space in 4.0.8 Created: 07/Aug/19 Updated: 09/Aug/19 Resolved: 09/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.0.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tanveer Madan Marate | Assignee: | Danny Hatcher (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Steps To Reproduce: | Run compact on the collections |
| Participants: |
| Description |
|
Hi, We are running a replicaset on MongoDB version 4.0.8 on Amazon Linux1 We have deleted 40% of data from all the collections of the database and dropped the custom indexes When we run compaction we do not see it releasing any space on the disk Any suggestions on this
|
| Comments |
| Comment by Danny Hatcher (Inactive) [ 09/Aug/19 ] |
|
The compact command can vary in terms of the disk space it releases. As you are using a replica set, I recommend instead performing a rolling initial sync one node at a time. This method releases the maximum possible disk space. If you have any questions about the process, I encourage you to ask our community by posting on the mongodb-user group or on Stack Overflow with the mongodb tag. |