[SERVER-35525] Consider converting WT tunables into MongoDB parameters Created: 10/Jun/18  Updated: 06/Dec/22  Resolved: 22/Jun/18

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

Type: Improvement Priority: Major - P3
Reporter: Dmitry Agranat Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: nonnyc, storage-engines
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Comments   
Comment by Bruce Lucas (Inactive) [ 11/Jun/18 ]

The concepts embodied in those parameters seem mostly pretty inherently WT-specific. I would be concerned whether an attempt to hide them behind something more generic will lose too much fidelity and make it difficult to achieve the desired tuning. I think there are two things that are requested here:

  • document the specific WT tunables that we have found customers need in a manner that reflects how they interact with the way MongoDB uses them
  • make it more convenient for customers to tune them by promoting them to first-class MongoDB parameters

Do these actually need to go through the API as such? Couldn't they be handled in the same way that we handle the existing WiredTiger-specific options today, like wiredTigerCacheSizeGB, wiredTigerJournalCompressor, wiredTigerDirectoryForIndexes, wiredTigerCollectionBlockCompressor, wiredTigerIndexPrefixCompression, etc.?

Comment by Eric Milkie [ 11/Jun/18 ]

By all storage engines, I am referring to putting something through MongoDB's generic pluggable storage API that will make sense for all storage engines. It will be up to each individual storage engine to decide how to implement the functionality, but it will be our jobs to ensure that the functionality isn't completely WiredTiger-centric.

Comment by Eric Milkie [ 11/Jun/18 ]

If we end up doing this, I prefer that we come up with some cover parameters that set underlying storage engine settings together as a group, rather than simply exposing internal storage engine tuning knobs to admins. We need to have parameters that make sense for all storage engines, not just WiredTiger.

Generated at Thu Feb 08 04:40:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.