[SERVER-72675] Values passed by --setParameter not applied Created: 10/Jan/23  Updated: 29/Oct/23  Resolved: 28/Apr/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72676 Remove redudant constraint check for ... Backlog
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-03-20, Execution Team 2023-05-01
Participants:

 Description   

There is at least one instance where --setParameter is not working as expected.

./build/install/bin/mongod --setParameter journalCommitInterval=200

Results in the journal flusher running every 100ms (default). By contrast

./build/install/bin/mongod --journalCommitInterval=200 

or using a config file works as expected.

Apparently the setParameter value is overwritten by the default value of the parameter in
https://github.com/10gen/mongo/blob/1eb33d31a32bb7d1a1a18e07c78239b90a9dd5d3/src/mongo/db/mongod_options.cpp#L433



 Comments   
Comment by Githook User [ 28/Apr/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-72675 Fix setParameter startup argument overwritten by default
Branch: master
https://github.com/mongodb/mongo/commit/06dca1aeaab8986647935b37ff9729455ce2a261

Comment by Matt Kneiser [ 10/Jan/23 ]

FYI, there's a TODO further up from October 2013:

// TODO: Integrate these options with their setParameter counterparts

Comment by Matthew Saltz (Inactive) [ 10/Jan/23 ]

This might be related to SERVER-72676

Generated at Thu Feb 08 06:22:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.