Refactor OpDebug to track multiple query stats entries

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      As part of collecting query stats for writes on the router, we need to be able to keep track of multiple different write statements, due to how write batching works.

      Instead of having a single implied query stats entry in OpDebug we need a map of query stats keys to an info structure where we can aggregate metrics from different shards. For the read side of things and for the shard role, they can continue to work as before, but will use just a single entry in this map.

            Assignee:
            Chris Wolff
            Reporter:
            Chris Wolff
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: