Include queryStatsMetrics in response when update is forwarded from router to primary shard

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

      Background

      There is a chance that a batched update command is rerouted to a primary shard, which will behave like a mongos as it invokes cluster::write() as well. In this case, the primary shard is required to include the metrics in the response (otherwise, the metrics will be lost between the primary shard and mongos). Currently,  the response generation ignores the queryStatsMetrics.

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

              Created:
              Updated:
              Resolved: