[SERVER-19483] Allow querying wiredTigerEngineRuntimeConfig via getParameter Created: 19/Jul/15 Updated: 12/Oct/17 Resolved: 02/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Andre de Frere | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Done | Votes: | 7 |
| Labels: | NewEng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Storage 2017-10-02, Storage 2017-10-23 | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
setting the wiredTigerEngineRuntimeConfig string in the shell, at the command line or in a config file does not change the config string when viewed through getParameter.
|
| Comments |
| Comment by Githook User [ 02/Oct/17 ] |
|
Author: {'email': 'daniel.gottlieb@mongodb.com', 'name': 'Daniel Gottlieb', 'username': 'dgottlieb'}Message: |
| Comment by Daniel Gottlieb (Inactive) [ 29/Sep/17 ] |
|
Pinging andre.defrere dmitry.agranat |
| Comment by Daniel Gottlieb (Inactive) [ 28/Sep/17 ] |
|
Hi alexander.gorrod andre.defrere dmitry.agranat, I'm looking into this ticket. I have a patch up that simply has getParameter on the runtime config return the last string successfully set. The last string set is also returned in the "was" field on followup setParameter calls. From my understanding, WiredTiger would still require changes to be able to ask it about settings dictated by other mechanisms. Otherwise, is a change of this form agreeable? Or should the ticket be put back into the backlog? |
| Comment by Alexander Gorrod [ 27/Jun/17 ] |
The places it has caused problems in the past is when configuration options are removed in more recent releases (which breaks applications that are explicitly setting them), or when default settings change and existing applications don't get the benefit from the change because they are explicitly using the old value.
I thought the goal was to extract the content of the user specified wiredTigerEngineRuntimeConfig setting. |
| Comment by Alexander Gorrod [ 26/Jun/17 ] |
That hasn't been what is wanted in the past. The defaults can change between releases, and including them in a string returned to the user can result in unexpected and undesired behavior. Are you sure that's what is being requested? |
| Comment by David Hows [ 21/Jun/17 ] |
|
Its worth noting here that MongoDB has a number of default configuration options set when using WiredTiger. It would be valuable to understand the use-case for this option so we know what to return. |
| Comment by Ramon Fernandez Marina [ 05/Aug/15 ] |
|
According to the description of this feature in |