-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
The docs about --repairDatabase https://docs.mongodb.com/manual/reference/command/repairDatabase/ has a section called "Using repairDatabase to reclaim disk space". I find there are some issues with this (very short, explanation-free) section:
You should not use repairDatabase for data recovery unless you have no other option.
The section is about reclaiming disk space, but the first paragraph is about data recovery. This feels out of place.
However, if you trust that there is no corruption and you have enough free space, then repairDatabase is the appropriate and the only way to reclaim disk space.
1. This paragraph has led to cases where users wanting to reclaim space simply doing --repairDatabase without understanding what it actually does (i.e. rebuilding the collection minus some corrupted documents). I'm not sure if the wording "the appropriate and the only way to reclaim disk space" is appropriate for this section.
2. Is this suggestion still valid for WiredTiger?
- is related to
-
DOCS-9714 Clarify operation of compact command with WiredTiger
- Closed
-
DOCS-9814 WiredTiger does not compact or reclaim space following a repair
- Closed
- related to
-
DOCS-10590 Issues with repairDatabase documentation
- Closed