[SERVER-24301] Increase max mmapv1 journal size in debug builds to 1GB Created: 26/May/16  Updated: 23/Nov/16  Resolved: 02/Jun/16

Status: Closed
Project: Core Server
Component/s: MMAPv1
Affects Version/s: 3.3.6
Fix Version/s: 3.2.8, 3.3.8

Type: Bug Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Robert Guo (Inactive)
Resolution: Done Votes: 0
Labels: code-only
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: TIG 15 (06/03/16), TIG 16 (06/24/16)
Participants:
Linked BF Score: 0

 Description   

FSM suites can cause the journal to grow above the current limit of 0.5GB



 Comments   
Comment by Githook User [ 07/Jun/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robertguo@me.com'}

Message: SERVER-24301 increase mmapv1 max journal size on debug builds

(cherry picked from commit 94bb6ab212c5f0baf67e7aff167fbf5c54db0637)
Branch: v3.2
https://github.com/mongodb/mongo/commit/3fd250ba74e52052ed92a442ff089c8e6b80a8b4

Comment by Githook User [ 02/Jun/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robertguo@me.com'}

Message: SERVER-24301 fix typo in error message
Branch: master
https://github.com/mongodb/mongo/commit/92781ea91516c14e63715fafa8868a505b8eda80

Comment by Robert Guo (Inactive) [ 27/May/16 ]

requesting backbport to 3.2 to fix a build failure we saw on the 3.2 branch.

Comment by Githook User [ 27/May/16 ]

Author:

{u'username': u'guoyr', u'name': u'Robert Guo', u'email': u'robertguo@me.com'}

Message: SERVER-24301 increase mmapv1 max journal size on debug builds
Branch: master
https://github.com/mongodb/mongo/commit/94bb6ab212c5f0baf67e7aff167fbf5c54db0637

Generated at Thu Feb 08 04:05:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.