Skip to content

DOCS-9714 Clarify operation of compact command with WiredTiger #3143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 4, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions source/reference/command/compact.txt
Original file line number Diff line number Diff line change
Expand Up @@ -153,10 +153,15 @@ To see how the storage space changes for the collection, run the
WiredTiger
``````````

On :ref:`WiredTiger <storage-wiredtiger>`, :dbcommand:`compact` will rewrite
the collection and indexes to minimize disk space by releasing unused disk space
to the system. This is useful if you have removed a large amount of data
from the collection, and do not plan to replace it.
On :ref:`WiredTiger <storage-wiredtiger>`, :dbcommand:`compact` attempts to
reduce the required storage space for data and indexes in a collection, releasing
unneeded disk space to the operating system. The effectiveness of this operation
is workload dependent and no disk space may be recovered. This command is useful
if you have removed a large amount of data from the collection, and do not plan
to replace it.

:dbcommand:`compact` does not require any additional disk space to run
on WiredTiger databases.

MMAPv1
``````
Expand Down