[DOCS-9267] WiredTiger Space Requirements & Behavior during repair and compact Created: 03/Nov/16 Updated: 30/Oct/23 Resolved: 03/Jan/18 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Vick Mena (Inactive) | Assignee: | Kevin Adistambha |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 7 weeks, 6 days ago | ||||||||
| Description |
|
Need some advise on our documentation for users looking to estimate their disk space requirements during a repair and compact with WiredTiger. Moreover, perhaps some clarifications on the behavior of those two operations when it comes to the WiredTIger storage engine. |
| Comments |
| Comment by Githook User [ 22/Dec/17 ] |
|
Author: {'name': 'Kevin Adistambha', 'email': 'kevinadi@gmail.com', 'username': 'kevinadi'}Message: |