Some data bearing node metrics aren't propogated through mongod when mongod acts as a router

XMLWordPrintableJSON

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

      If mongos only targets shard0 with a $lookup, and shard0 then acts as a router and targets shard1 for the foreign coll lookup, most data bearing metrics (i.e. bytesRead) from shard1 won't be aggregated back to shard0. Only metrics that are propagated through planSummaryStats (like docsExamined) are collected correctly. See attached test for example of bytesRead not being aggregated correctly, and docsExamined is aggregated correctly.

            Assignee:
            Unassigned
            Reporter:
            Erin Zhu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: