[SERVER-4338] Compact command results in (much) larger database Created: 21/Nov/11 Updated: 22/Nov/11 Resolved: 22/Nov/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Joost de Vries | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.6 |
||
| Operating System: | Linux |
| Participants: |
| Description |
|
After I've run an inline compaction, the DB actually grows in size. I've seen this happening on my production environment (where I actually ran out of RAM because of this) and I've just reproduced it on my development environment. After running db.repairDatabase() the size shrinks back. Below is the Mongo shell output: > show dbs > show dbs > db.stats() |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 22/Nov/11 ] |
|
compact has to increase db size originally so it has space to do the copy. Also, there is an issue with repeated compacts, see: SERVER:3791 |