[SERVER-47609] Execution Architecture Guide: Journaling Created: 16/Apr/20  Updated: 29/Oct/23  Resolved: 11/Jun/20

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-06-15
Participants:

 Description   

Rough starting outline:

Journaling
    (Durability can be guaranteed by simply flushing the journal to disk, not the writes themselves.)
    (What we do when journaling is disabled -- take full data checkpoints. Periodically flush to ensure minimal loss of data.)

Definitely feel free to alter the layout and file additional tickets split the work into more manageable units. Please add topics if you can think of any. This outline is meant only to be a starting point.

A couple helpful links for markdown basics:
https://www.markdowntutorial.com/
https://gist.github.com/asabaylus/3071099
https://markdownlivepreview.com/



 Comments   
Comment by Githook User [ 11/Jun/20 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-47609 Execution Architecture Guide: Journaling
Branch: master
https://github.com/mongodb/mongo/commit/961dd62e0994a22800d92be1664685849cbccb62

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