[DOCS-13443] Provide guidance for sizing journal folder Created: 23/Feb/20  Updated: 30/Oct/23

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

Type: Improvement Priority: Major - P3
Reporter: Shakir Sadikali Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: docs-administration
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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

 Description   

Description

We recommend moving the journal to a separate mount for performance reasons and as part of our best practices but omit providing guidance on sizing of this mount.   The consequence of this is the generation of unnecessary  Support cases and inconsistent responses.

Under steady-state conditions we need to keep at least "dirty data generated and journaled between checkpoints". 

Starting in 4.0 we journal only OpLog entries.  Therefore, using OpLog churn metrics as a proxy we can provide some actual guidance.

Under steady-state I'd use 10 min * oplog churn/min.  I would then recommend the customer think about downtime requirements where a majority commit point is not moved forward for some extended period of time (due to maintenance or downtime).  In that case, we should plan for hours to days of "window" and size accordingly.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Education Bot [ 31/Oct/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 08:07:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.