[SERVER-58838] Provide access to wiredTigerEngineRuntimeConfig also in the config file Created: 26/Jul/21 Updated: 27/Oct/23 Resolved: 28/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | John Moser | Assignee: | Dmitry Agranat |
| Resolution: | Community Answered | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
It has been proposed to apply : db.adminCommand({setParameter: 1, wiredTigerEngineRuntimeConfig: "file_manager (close_idle_time=30,close_scan_interval=30,close_handle_minimum=100)" }) If you run lets say 100 clusters of MongoDB Servers/Operators then it is not a viable option to apply 100x the command above. Please make this config item and others also available as a configurable parameter. |
| Comments |
| Comment by John Moser [ 27/Jul/21 ] | |||||
|
Thanks Dima - I made a mistake (see https://jira.mongodb.org/browse/SERVER-58818). file_manager params work !
Please close this ticket. | |||||
| Comment by Dmitry Agranat [ 27/Jul/21 ] | |||||
|
Hi jamoser42@gmail.com, I am not sure what do you mean by "must be configurable by deployment" but here is an example how you can use this parameter in your config file:
Regards, | |||||
| Comment by John Moser [ 27/Jul/21 ] | |||||
|
To be specific it's about this configuration : file_manager (close_idle_time=###,close_scan_interval=###,close_handle_minimum=###) Imo this must be configurable by deployment.
|