[SERVER-43075] MongoDB 4.2 cannot use storage.journal.commitIntervalMs param in yaml config file. Created: 29/Aug/19  Updated: 29/Oct/23  Resolved: 30/Aug/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 4.2.0
Fix Version/s: 4.2.1, 4.3.1

Type: Bug Priority: Critical - P2
Reporter: jackin huang Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File test.yml    
Issue Links:
Backports
Depends
Documented
is documented by DOCS-12999 Investigate changes in SERVER-43075: ... Closed
Related
related to SERVER-35112 Remove MMAPv1 code Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Execution Team 2019-09-09
Participants:

 Description   

I use mongod of 4.2.0 to start MongoDB server with 'mongod -f test.yml'.

But something went wrong, like:

MacBook-Pro:mongo37017 jackin$ mongod -f test.yml
Unrecognized option: storage.journal.commitIntervalMs
try 'mongod --help' for more information

Use the 4.0.5 version of mongod to start normally.

This looks like a bug in 4.2.0 mongod.

Attachment is my configuration file.

THX.



 Comments   
Comment by Githook User [ 30/Aug/19 ]

Author:

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

Message: SERVER-43075: Reintroduce startup options for journal flush frequency.

They were mistakenly removed when purging MMAPv1 options.
Branch: master
https://github.com/mongodb/mongo/commit/15e977e930284216f422aa1dd373a3284b74faf5

Comment by Githook User [ 30/Aug/19 ]

Author:

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

Message: SERVER-43075: Reintroduce startup options for journal flush frequency.

They were mistakenly removed when purging MMAPv1 options.

(cherry picked from commit 37401025da331437884a57bae3af8c7ebbf1d8e1)
Branch: v4.2
https://github.com/mongodb/mongo/commit/c20352e2cdea8e52c5051afae19380d2788a301f

Comment by jackin huang [ 30/Aug/19 ]

Okay, Thank you very much.

Comment by Eric Milkie [ 29/Aug/19 ]

Hi jackin huang,
Thanks for reporting this issue; indeed it was mistakenly removed in MongoDB 4.2. We're working on adding it back for 4.2.1. In the meantime, since you are setting the commit interval to "100" which is already the default, it would be safe to remove that particular line in your YAML config file with no ill effects.

Comment by Danny Hatcher (Inactive) [ 29/Aug/19 ]

Thanks for reporting this issue. We'll look into it.

Comment by jackin huang [ 29/Aug/19 ]

I use mongod version.

db version v4.2.0
git version: a4b751dcf51dd249c5865812b390cfd1c0129c30
allocator: system
modules: none
build environment:
distarch: x86_64
target_arch: x86_64

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