Skip to content

Commit e6eb1e7

Browse files
Amarkay-kim
authored andcommitted
DOCS-11357 Remove mention of WiredTiger snapshotting after 2 GB of journal data
1 parent 1ac6d9f commit e6eb1e7

File tree

1 file changed

+3
-5
lines changed

1 file changed

+3
-5
lines changed

source/includes/extracts-wired-tiger.yaml

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -168,7 +168,7 @@ content: |
168168
---
169169
ref: wt-cache-default-setting
170170
content: |
171-
171+
172172
Starting in 3.4, the WiredTiger internal cache, by default, will use
173173
the larger of either:
174174
@@ -184,17 +184,15 @@ content: |
184184
ref: wt-snapshot-frequency
185185
content: |
186186
MongoDB configures WiredTiger to create checkpoints (i.e. write the
187-
snapshot data to disk) at intervals of 60 seconds or 2 gigabytes of
188-
journal data.
187+
snapshot data to disk) at intervals of 60 seconds.
189188
---
190189
ref: wt-journal-frequency
191190
content: |
192191
- .. versionadded:: 3.2
193192
Every 50 milliseconds.
194193
195194
- MongoDB sets checkpoints to occur in WiredTiger on user data at an
196-
interval of 60 seconds or when 2 GB of journal data has been written,
197-
whichever occurs first.
195+
interval of 60 seconds.
198196
199197
- If the write operation includes a write concern of :writeconcern:`j:
200198
true <j>`, WiredTiger forces a sync of the WiredTiger journal files.

0 commit comments

Comments
 (0)