Investigate whether a better mechanism for exporting WiredTiger configuration data exists

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Statistics
    • None

      A reasonable number of WiredTiger statistics track configuration settings, e.g. "wt cache maximum bytes configured". A lot of these are also unable to be changed at runtime, and therefore don't need to be continually reported via statistics, while FTDC compression does handle this and make them a very small amount of the data reported it would be good if we had a different mechanism for WiredTiger configurations to be reported to the application, and made visible in T2.

      Some of this exists already as the MongoDB configuration WiredTiger was started with is available in the T2 info panel but it is likely that some of these settings are not tuned by MongoDB and therefore not exposed in that panel.

      Scope:

      • Investigate whether a different path to return WiredTiger metrics exists
      • If so:
        • Identify the set of statistics that track WiredTiger config options
        • Return them via the new / other path and remove them from stat_data.py

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: