[DOCS-9301] Update to repairDatabase documentation Created: 11/Nov/16  Updated: 30/Oct/23  Resolved: 03/Aug/17

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Major - P3
Reporter: Kevin Adistambha Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to DOCS-10590 Issues with repairDatabase documentation Closed
is related to DOCS-9714 Clarify operation of compact command ... Closed
is related to DOCS-9814 WiredTiger does not compact or reclai... Closed
Participants:
Days since reply: 7 years, 13 weeks, 6 days ago

 Description   

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?


Generated at Thu Feb 08 07:58:02 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.