[DOCS-1418] Create tutorial for separate data/db/journal/log directories Created: 20/Apr/13  Updated: 30/Oct/23  Resolved: 27/Jul/16

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

Type: Improvement Priority: Minor - P4
Reporter: J Rassi Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: storage
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on DOCS-1420 Production Notes missing suggestion f... Closed
Related
related to DOCS-1607 Moving journal to a separate drive Closed
Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

Need to do DOCS-1420 first, then...

Should expand on the old "Journaling" page, which had the following section:

The journal Subdirectory
You may wish, before starting mongod to symlink the journal/ directory to a dedicated hard drive to speed the frequent (fsynced) sequential writes which occur to the current journal file.

After creating the tutorial, link to it from the production notes.



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed for housekeeping on 7/27/2016 by Emily Hall.
If you require additional support, please open a new ticket for prioritization.
Thanks,
Emily

Comment by Brandon Newell [ 18/Apr/16 ]

Redirect journal folder for write intensive workloads
In this scenario, we will mount a new volume that will be dedicated to the journal. We will mount this new volume as /journal
If you installed MongoDB via one of our packages (RPM,DEB), the default location of the database will be in the following path:

/var/lib/mongo

As journaling is enabled by default, the default journal path would be:

/var/lib/mongo/journal

As a reminder, in this example you should have mounted the new journal path as /journal
Now we create a symbolic link from the default journal path /var/lib/mongo/journal to the volume called /journal using the Linux 'ln' command.

ln -s /journal /var/lib/mongo/

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