Query stats execution metrics are zero for retryable timeseries updates on mongos

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Overview

      Retryable updates on time-series collections on mongos are dispatched through an internal transaction (AnalysisType::kInternalTransaction). The shard computes query stats execution metrics, but the inner router layer in WriteBatchResponseProcessor::generateClientResponseForBatchWriteCommand only echoes those metrics back to the parent router when the command is forwarded from a router. For the internal-transaction re-route that condition is false, so the metrics are dropped and the router records the query stats entry with zeroed keysExamined, docsExamined, nMatched, and nModified.

      Split out from SERVER-121266, which remains open for the retry de-duplication issue (execCount increments on retry).

            Assignee:
            Chi-I Huang
            Reporter:
            Chi-I Huang
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: