Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-36099

FTDC for mongos is unworkably large for large installations

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.14, 4.1.12, 4.0.11
    • Component/s: Diagnostics
    • Labels:
      None
    • Operating System:
      ALL
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Security 2018-09-10, Service Arch 2019-04-22, Service Arch 2019-05-06, Service Arch 2019-05-20, Service Arch 2019-06-03

      Description

      For installations with hundreds of nodes, the number of metrics collected by mongos FTDC can be unworkably large. For example one cluster with ~500 nodes collects ~20k metrics (per sample), mostly due to connPoolStats. This creates problems for downstream consumers of this information, and also will severely limit the retention period for FTDC data.

      This is because connPoolStats records several metrics per (pool, host) pair. Some possible solutions

      • aggregate the information in some way before recording it to avoid the combinatorial explosion
      • remove this information altogether
      • add an option to remove it (off by default to avoid catching customers unawares?)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jesse A. Jesse Jiryu Davis
              Reporter:
              bruce.lucas Bruce Lucas
              Participants:
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: