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.

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

Conversation

techwriter13
Copy link

@techwriter13 techwriter13 commented Nov 7, 2017

Clarified the difference between the behavior of WiredTiger and MMAPv1 when journaling is turned on.


This change is Reviewable

@atsansone atsansone changed the title Forgot to add the link to the Journaliing article. (DOCS-10331): Forgot to add the link to the Journaliing article. Nov 15, 2017
@atsansone atsansone changed the title (DOCS-10331): Forgot to add the link to the Journaliing article. (DOCS-10331): Forgot to add the link to the Journaling article. Nov 15, 2017
@@ -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.

@@ -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.

If you could make the aforementioned changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants