Skip to content

DOCS-11357 Remove mention of WiredTiger snapshotting after 2 GB of jo… #3250

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 2 commits into from
Feb 28, 2018
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
14 changes: 7 additions & 7 deletions source/includes/extracts-wired-tiger.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ content: |
---
ref: wt-cache-default-setting
content: |

Starting in 3.4, the WiredTiger internal cache, by default, will use
the larger of either:

Expand All @@ -183,18 +183,18 @@ content: |
---
ref: wt-snapshot-frequency
content: |
MongoDB configures WiredTiger to create checkpoints (i.e. write the
snapshot data to disk) at intervals of 60 seconds or 2 gigabytes of
journal data.
.. versionchanged:: 3.6
MongoDB configures WiredTiger to create checkpoints (i.e. write the
snapshot data to disk) at intervals of 60 seconds.
---
ref: wt-journal-frequency
content: |
- .. versionadded:: 3.2
Every 50 milliseconds.

- MongoDB sets checkpoints to occur in WiredTiger on user data at an
interval of 60 seconds or when 2 GB of journal data has been written,
whichever occurs first.
- .. versionchanged:: 3.6
MongoDB sets checkpoints to occur in WiredTiger on user data at an
interval of 60 seconds.

- If the write operation includes a write concern of :writeconcern:`j:
true <j>`, WiredTiger forces a sync of the WiredTiger journal files.
Expand Down