[SERVER-13455] configuration option to use a separate directory for the journal Created: 02/Apr/14  Updated: 10/May/22

Status: Backlog
Project: Core Server
Component/s: Admin
Affects Version/s: 2.6.0-rc2
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Mark Callaghan Assignee: Brian Lane
Resolution: Unresolved Votes: 30
Labels: asya
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-21151 Config option to support custom journ... Closed
Problem/Incident
Related
related to SERVER-36216 Add API in BackupCursorService for ne... Closed
related to SERVER-13182 How to write journal directory in a s... Closed
is related to SERVER-36882 Include "WiredTigerTmplog" as a valid... Closed
is related to SERVER-24110 Explicit control over directories cre... Closed
Sprint: Server 2.7.6, Storage NYC 2018-07-30, Storage NYC 2018-08-13, Storage NYC 2018-08-27
Participants:
Case:
Linked BF Score: 41

 Description   

See SERVER-13182 for background and http://dom.as/2014/03/31/mongo-io. We want an option to use a different directory for the journal and prefer not to use symbolic links or mount $dbpath/journal as a separate filesystem.



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Githook User [ 29/Aug/18 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: Revert "SERVER-13455 add new configuration option for mongod to allow separate journal directory for WT"

This reverts commit b20d3b5294b09a87de3aae729af3f2e9534a6724.
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/82a943cc82d16b45c8abd3a3e88790cf63a21e32

Comment by Daniel Gottlieb (Inactive) [ 29/Aug/18 ]

Unfortunately, we've had to revert this change for the time being. Allowing this option, while providing users safety in the event of incorrect configuration, required persisting filesystem paths to disk as part of some metadata. Taking a physical backup requires copying this metadata. If the journal path is configured as an absolute path and the data was copied to another directory on the same machine, the metadata files for both sets of data would reference the same journal files. If the data files were copied to a different machine, the user would have to take care in placing the journal files in the same directory as the source.

Comment by Githook User [ 29/Aug/18 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: Revert "SERVER-13455 Add new configuration option for mongod to allow separate journal directory for WT"

This reverts commit d3656459d016d6a1be0788acfe3276734ab59210.
Branch: master
https://github.com/mongodb/mongo/commit/fa5f357a688e0eb5c4d260cf86997495854104b1

Comment by Githook User [ 24/Aug/18 ]

Author:

{'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}

Message: SERVER-13455 Add new configuration option for mongod to allow separate journal directory for WT
Branch: master
https://github.com/mongodb/mongo/commit/d3656459d016d6a1be0788acfe3276734ab59210

Comment by Githook User [ 24/Aug/18 ]

Author:

{'name': 'Dewal Gupta', 'email': 'dewal.gupta@10gen.com', 'username': 'dewalg'}

Message: SERVER-13455 add new configuration option for mongod to allow separate journal directory for WT
Branch: master
https://github.com/10gen/mongo-enterprise-modules/commit/b20d3b5294b09a87de3aae729af3f2e9534a6724

Comment by Matthieu Rigal [ 13/Aug/14 ]

Yes, having a journalpath or similar option in the configuration would be very useful !

Generated at Thu Feb 08 03:31:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.