@@ -122,14 +122,29 @@ For details, see :ref:`manage-journaling-change-wt-journal-compressor`.
122
122
Journal File Size Limit
123
123
```````````````````````
124
124
125
- WiredTiger journal files for MongoDB have a maximum size limit of
126
- approximately 100 MB .
125
+ WiredTiger journal files have a maximum size limit of approximately 100 MB.
126
+ Once the file exceeds that limit, WiredTiger creates a new journal file .
127
127
128
- - Once the file exceeds that limit, WiredTiger creates a new journal
129
- file.
128
+ WiredTiger automatically removes old journal files and maintains only
129
+ the files needed to recover from the last checkpoint. To determine how much
130
+ disk space to set aside for journal files, consider the following:
131
+
132
+ - The default maximum size for a checkpoint is 2 GB
133
+ - Additional space may be required for MongoDB to write new journal
134
+ files while recovering from a checkpoint
135
+ - MongoDB compresses journal files
136
+ - The time it takes to restore a checkpoint is specific to your use case
137
+ - If you override the maximum checkpoint size or disable compression, your
138
+ calculations may be significantly different
139
+
140
+ For these reasons, it is difficult to calculate exactly how much additional
141
+ space you need. Over-estimating disk space is always a safer approach.
142
+
143
+ .. important::
144
+
145
+ If you do not set aside enough disk space for your journal
146
+ files, the MongoDB server will crash.
130
147
131
- - WiredTiger automatically removes old journal files to maintain only
132
- the files needed to recover from last checkpoint.
133
148
134
149
Pre-Allocation
135
150
``````````````
0 commit comments