Investigate changes in SERVER-120369: Server status metrics for CBR

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Tools and Replicator

      Original Downstream Change Summary

      This change adds several new serverStatus metrics in the following sections:
      serverStatus.metrics.query.cbr
      serverStatus.metrics.query.multiPlanner
      serverStatus.metrics.query.subPlanner

      Description of Linked Ticket

      Define basic planning-related server status metrics for CBR. I'm thinking of the equivalents to these ones:

      https://github.com/10gen/mongo/blob/4fc1de8141b668f5ffb5bb2d2a5f576e3e30766b/src/mongo/db/exec/classic/multi_plan.cpp#L86.

      This includes adding CBR equivalents of these:

      • query.multiPlanner.classicMicros
      • query.multiPlanner.classicCount
      • query.multiPlanner.histograms.classicMicros
      • query.multiPlanner.histograms.classicWorks

      Plus:

      • We need to decide whether existing metrics should include CBR or they should be split out.
      • We need to make a decision about how to count multiplanner metrics for the cases where MP is used but it falls back to CBR and CBR makes the planning decision.

      This ticket should review all the MP serverstatus metrics and ensure they make sense after introducing CBR, and that we have equivalents for CBR.

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: