[SERVER-73017] Aggregate telemetry metrics in client cursor rather than in telemetry store Created: 18/Jan/23  Updated: 29/Oct/23  Resolved: 21/Feb/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Maddie Zechar Assignee: Will Buerger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Assigned Teams:
Query Optimization
Backwards Compatibility: Fully Compatible
Sprint: QO 2023-02-06, QO 2023-02-20, QO 2023-03-06
Participants:
Linked BF Score: 0

 Description   

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



 Comments   
Comment by Githook User [ 21/Feb/23 ]

Author:

{'name': 'Will Buerger', 'email': 'will.buerger@mongodb.com', 'username': 'wbuerger46'}

Message: SERVER-73017: Aggregate telemetry metrics in client cursor
Branch: master
https://github.com/mongodb/mongo/commit/e402a70bd12b068e9f1706393f73efb0337e37d7

Generated at Thu Feb 08 06:23:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.