Skip to content

DOCS-10720 Clarify 'file bytes available for reuse' in WT FAQ #3087

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.

Sign up for GitHub

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
Nov 7, 2017
Merged

DOCS-10720 Clarify 'file bytes available for reuse' in WT FAQ #3087

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
19 changes: 19 additions & 0 deletions source/faq/storage.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,25 @@ intervals or condition:

.. include:: /includes/extracts/wt-journal-frequency.rst

.. _faq-wt-reclaim-disk-space:

How do I reclaim disk space in WiredTiger?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The WiredTiger storage engine maintains lists of empty records in data
files as it deletes documents. This space can be reused by WiredTiger,
but will not be returned to the operating system unless under very
specific circumstances.

The amount of empty space available for reuse by WiredTiger is reflected
in the output of :method:`db.collection.stats()` under the heading
``wiredTiger.block-manager.file bytes available for reuse``.

To allow the WiredTiger storage engine to release this empty space to the
operating system, you can de-fragment your data file. This can be achieved
using the :dbcommand:`compact` command. For more information on its behavior
and other considerations, see :dbcommand:`compact`.

MMAPv1 Storage Engine
---------------------

Expand Down