Skip to content

Commit 0afeacc

Browse files
kevinadikay-kim
authored andcommitted
DOCS-10720 Clarify 'file bytes available for reuse' in WT FAQ
1 parent 7d3d4e3 commit 0afeacc

File tree

1 file changed

+19
-0
lines changed

1 file changed

+19
-0
lines changed

source/faq/storage.txt

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,25 @@ intervals or condition:
8484

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

87+
.. _faq-wt-reclaim-disk-space:
88+
89+
How do I reclaim disk space in WiredTiger?
90+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
91+
92+
The WiredTiger storage engine maintains lists of empty records in data
93+
files as it deletes documents. This space can be reused by WiredTiger,
94+
but will not be returned to the operating system unless under very
95+
specific circumstances.
96+
97+
The amount of empty space available for reuse by WiredTiger is reflected
98+
in the output of :method:`db.collection.stats()` under the heading
99+
``wiredTiger.block-manager.file bytes available for reuse``.
100+
101+
To allow the WiredTiger storage engine to release this empty space to the
102+
operating system, you can de-fragment your data file. This can be achieved
103+
using the :dbcommand:`compact` command. For more information on its behavior
104+
and other considerations, see :dbcommand:`compact`.
105+
87106
MMAPv1 Storage Engine
88107
---------------------
89108

0 commit comments

Comments
 (0)