Skip to content

(DOCS-10331): Forgot to add the link to the Journaling article. #3088

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

Open
wants to merge 1 commit into
base: v6.1
Choose a base branch
from
Open

(DOCS-10331): Forgot to add the link to the Journaling article. #3088

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
6 changes: 6 additions & 0 deletions source/reference/write-concern.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,12 @@ the write operation has been written to the :doc:`journal
configuration setting determines the behavior. See
:ref:`wc-ack-behavior` for details.

- The :doc:`WiredTiger </core/wiredtiger>` and :doc:`MMAPv1 </core/mmapv1>`
storage engines handle setting a write concern that includes ``j: true``
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This sentence makes it sound like storage engines set a write concern.

I think we can just simplify and get to the meat:

  • For a write concern that includes j: true,

    • :doc:WiredTiger </core/wiredtiger> forces an immediate, synchronous journal flush.
    • :doc:MMAPv1 </core/mmapv1> waits for the next scheduled journal flush.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you could make the aforementioned changes

differently. ``WiredTiger`` forces an immediate, synchronous journal
flush while ``MMAPv1`` waits for the next scheduled journal flush. See
:doc:`journaling </core/journaling>` for details.

.. _wc-wtimeout:

``wtimeout``
Expand Down