determine storageEngine specificity in docs (DOCS-4856)

[DOCS-4681] update read isolation docs for wiredtiger Created: 16/Jan/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: mongodb-3.0
Fix Version/s: Server_Docs_20231030

Type: Sub-task Priority: Major - P3
Reporter: Mark Callaghan Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: groom
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-16609 Add ability to configure WT asynchron... Closed
Documented
documents SERVER-16609 Add ability to configure WT asynchron... Closed
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago

 Description   

See https://jira.mongodb.org/browse/DOCS-2908. In mmapv1 changes are visible before the journal is forced to disk even when j:true is used on the write because this is how mmapv1 behaves. But I assume that MongoDB+WiredTiger does not release row/doc locks until the redo log is written, and if j:true is also set then changes are not visible until they are durable.

If true, then the docs should be updated and see https://jira.mongodb.org/browse/DOCS-2908 for pointers to the docs for mmapv1.



 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!

Comment by Asya Kamsky [ 16/Jan/15 ]

Linking to implementation ticket that this ticket depends on.

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