[DOCS-9814] WiredTiger does not compact or reclaim space following a repair Created: 24/Jan/17  Updated: 23/Aug/17  Resolved: 03/Aug/17

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

Type: Bug Priority: Major - P3
Reporter: David Hows 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 SERVER-27689 WiredTiger disk usage stats output do... Closed
related to DOCS-9301 Update to repairDatabase documentation Closed
is related to DOCS-10590 Issues with repairDatabase documentation Closed
Participants:
Days since reply: 7 years, 3 weeks, 1 day ago
Story Points: 0.15

 Description   

WiredTiger does not compact or reclaim space following a repair

Currently our documentation is incorrect; See the following page
https://docs.mongodb.com/manual/reference/command/repairDatabase/

This page states that the following will occur:

  1. Repair will reclaim disk space
  2. Repair will run a compact as part of the process

These functions are not executed in this manner when using WiredTiger.

To reclaim disk space on WiredTiger, you need to run the compact command not the repair command.



 Comments   
Comment by Ravind Kumar (Inactive) [ 24/Jan/17 ]

Clarification: This functionality is correct for MMAPv1

ToDo:

  • Split behavior section into WT and MMAPv1, specifically for addressing this divergence. Other shared information can stay as-is
  • WT subsection should specify that repairDatabase does not compact files
  • WT subsection should link to compact
  • Move existing behavior regarding compact into MMAPv1 subsection
Generated at Thu Feb 08 07:59:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.