[SERVER-57747] Measure latency/throughput of ReshardingTxnCloner::_getNextRecord Created: 16/Jun/21  Updated: 06/Dec/22  Resolved: 09/Jun/22

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

Type: Improvement Priority: Major - P3
Reporter: Lamont Nelson Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Won't Do Votes: 0
Labels: PM-234, PM-234-T-metrics, bkp, sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-57742 Create a non-specialized version of t... Closed
Related
is related to SERVER-64388 Track and Report New Recipient Latenc... Closed
Assigned Teams:
Sharding NYC
Backport Requested:
v5.0
Participants:

 Description   
  • Should collect latency information as a histogram with coarse grained buckets (0-10ms,11-100ms,101-1000ms, 1001-10000ms, 10001+ms)
  • Should track total number of invocations that complete
  • Should report these metrics in serverStatus to be consumed by FTDC.
  • Should report these metrics in currentOp if there is a resharding operation currently in progress.

https://github.com/mongodb/mongo/blob/6659e192ee5feceda14bebe1cb22f219d5d765fd/src/mongo/db/s/resharding/resharding_txn_cloner.cpp#L151


Generated at Thu Feb 08 05:42:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.