[DOCS-6905] Updates to 'Journaling' documentation Created: 05/Jan/16  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: Task Priority: Major - P3
Reporter: Ronan Bohan Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

On the Journaling page: https://docs.mongodb.org/manual/core/journaling/

Journaling and WiredTiger section:

However, if MongoDB exits unexpectedly in between checkpoints, journaling is required to recover information that occurred after the last checkpoint.

This isn't quite right. It is for a standalone instance, but for a replica set a node can generally recover from the last checkpoint via normal replication.

Journaling Process

With journaling, WiredTiger creates a log record per transaction.

The word 'transaction' can lead to problems. While WiredTiger implemented transactions underneath the database there are no database level transactions. We should either change the word transaction (to something like 'operation') or clarify that transaction is a WiredTiger specific term.



 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:53:12 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.