[DOCS-6485] Comment on: "manual/core/write-concern.txt" Created: 29/Oct/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: bite-sized, docs-triage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.mongodb.org/manual/core/write-concern/


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769
Story Points: 0.25

 Description   

Is this article correct if you're using WiredTiger?

From what I've read about WiredTiger, there isn't a concept of a journal which is flushed to disk like a memory mapped file would be.

See - http://www.slideshare.net/JonRangel/let-the-tiger-roar-mongodb-30-wiredtiger

On slide 17 - It states "consistency without journalling":
On slide 20 - It states "no journal commit interval: writes are written to the journal as they come in"

So, in this case, is Acknowledged write concern the same as Journaled under WiredTiger?

Also, in MMAPv1, when writes are Acknowledged, they sit in RAM before flushing to the journal, but in WiredTiger, if writes really are journaled "as they come in" according to the presentation, then the information on https://docs.mongodb.org/manual/faq/concurrency/ could be wrong.

In particular, the section of "Can reads see changes that have not been committed to disk?" states that dirty reads (read uncommitted) are possible, but the presentation here seems to suggest that it's not possible under WiredTiger.

See slide 13 - where it says "In-memory consistency" and slide 17 where it states that "Readers see the version that was committed before the operation started".

http://www.slideshare.net/wiredtiger/mongo-db-worldwiredtiger?related=3

Some clarity on the behaviour here is essential for me.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:52:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.