[SERVER-3302] settings to not roll over journal files Created: 20/Jun/11  Updated: 06/Dec/22  Resolved: 14/Sep/18

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

Type: Improvement Priority: Minor - P4
Reporter: Eliot Horowitz (Inactive) Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 2
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-7103 Consider adding a framework of using ... Closed
Assigned Teams:
Storage Execution
Participants:
Case:

 Description   

Would be really helpful to have a transient setting to not roll over journal files.

The you can:
1) set flag
2) copy data
3) copy journal
4) turn off flag

and end up with a guaranteed clean snapshot



 Comments   
Comment by Dwight Merriman [ 04/Sep/11 ]

implementation is incomplete so reopened.

Comment by Tony Hannan [ 19/Aug/11 ]

Added this method to backup documentation: http://www.mongodb.org/display/DOCS/Backups

Comment by Dwight Merriman [ 16/Aug/11 ]

would be good to document if it actually worked.
just fixed it. and added a (very incomplete) js test

Comment by auto [ 16/Aug/11 ]

Author:

{u'login': u'dwight', u'name': u'Dwight', u'email': u'dwight@10gen.com'}

Message: fix ageoutjournalfiles parameter setting bug SERVER-3302
Branch: master
https://github.com/mongodb/mongo/commit/eaf7bd21e5f9cc0ecfdc14926a82d0642d3720c1

Comment by Tony Hannan [ 16/Aug/11 ]

Shouldn't this be documented on http://www.mongodb.org/display/DOCS/Backups?

Comment by Dwight Merriman [ 22/Jun/11 ]

https://github.com/mongodb/mongo/commit/add206436e566d6659d5e1f00dbc6e63c6dcd436

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