Aggregate telemetry metrics in client cursor rather than in telemetry store

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • Fully Compatible
    • QO 2023-02-06, QO 2023-02-20, QO 2023-03-06
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Rather than rate limit getMores, we will aggregate telemetry metrics in client cursor land to reduce contention. Client cursor will pass the aggregated metrics across getMores until cursor is destroyed (exhausted or killed/abandoned). Will only write to telemetry store once the cursor is destroyed

            Assignee:
            Will Buerger
            Reporter:
            Maddie Zechar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: