[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: |
|
||||
| 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: |