[SERVER-56653] Storage "Opening WiredTiger" section does not reflect a change to the WiredTiger parameters Created: 05/May/21  Updated: 27/Oct/23  Resolved: 30/Nov/22

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

Type: Bug Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Gregory Wlodarek
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2021-05-06 at 10.50.40.png     PNG File Screen Shot 2021-05-06 at 11.01.16.png     PNG File Screen Shot 2021-05-06 at 11.24.52.png    
Issue Links:
Related
Operating System: ALL
Sprint: Execution Team 2022-12-12
Participants:
Case:

 Description   

After changing a WiredTiger parameter, this is being reflected by the Options set by command line but not by the Opening WiredTiger section



 Comments   
Comment by Eric Milkie [ 06/May/21 ]

I don't think we should be supporting any mixed use of numeric parameters with free-form wiredTiger*configString parameters. You must use either one type or the other, and they will not be synchronized between each other. Using the numeric parameters is recommended.

Comment by Louis Williams [ 05/May/21 ]

The confusion here is that user-provided config strings are appended at the end of MongoDB's default config string. This works because WT overwrites config options when it sees duplicate parameters later on in the string. This actually works very well for MongoDB because it means we don't have to do any string parsing to determine whether a user has provided duplicate options. We can just pass directly to WT and expect it to work.

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