Prevent MP from incrementing "hitWorksLimit" server status during capped MP trials

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we do the capped MP trials in CBR fallback, we should avoid incrementing the "hitWorksLimit" server status metric if we exhaust the limited works budget. This is because, exhausting the works limit in the capped MP trials will result in us either falling back to CBR, in which case we do not want to update any of the MP metrics or doing full MP in which case the metric updates will be handled correctly.

      We could achieve this by passing through some boolean when calling MultiPlanStage::runTrials() that indicates whether or not we should increment this metric.

      If we fill first batch or hit EOF in MP capped trials we should still update those metrics, however.

            Assignee:
            Naafiyan Ahmed
            Reporter:
            Naafiyan Ahmed
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: