[DOCS-1877] Comment on: "manual/core/write-concern.txt" Created: 02/Sep/13  Updated: 03/Nov/17  Resolved: 22/Jan/14

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: v1.2

Type: Improvement Priority: Major - P3
Reporter: Christoph Menge Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 1
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

N/A

Location: http://docs.mongodb.org/manual/core/write-concern/
User-Agent: Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.16
Referrer: http://stackoverflow.com/questions/18488209/does-mongodb-journaling-guarantee-durability/18489344
Screen Resolution: 1920 x 1080
repo: docs
source: core/write-concern


Participants:
Days since reply: 10 years, 24 weeks, 2 days ago

 Description   

The description for the section "Journaled" is misleading, at least if I understand the source code correctly. The documentation says:

"However, there is a window between journal commits when the write operation is not fully durable". That probably refers to a mongod running with journaling on that accepts a write that does NOT use the j:true write concern. In that case, there's a chance of the write getting lost since the last journal commit.

If j:true is specified, however, the write operation (or, more precisely, the getLastError command) will block until the server's durability thread has flushed all pending changes to disk, so the client can be sure that the data has been written.


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