[DOCS-6423] Explain why disk space usage recovery Created: 21/Oct/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Docs Collector User (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | bite-sized, docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
linux Location: https://docs.mongodb.org/manual/faq/storage/#faq-disk-size |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.25 |
| Description |
|
How can this possibly be correct behaviour. It seems that the database grows continuously and the only way to recover the space is to take it off-line. I have a database with 3GB of used space and 29GB of disk space used. There is absolutely no obvious reason why this might be the case. Nothing on the web hints at what is going on other than the stack-overflow page from 2011 which basically admits that this is hopeleess. This makes mongo completely useless for almost any application. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |