[SERVER-80173] Write $currentOp Metrics for Resharding at End of Operation Created: 16/Aug/23  Updated: 18/Aug/23  Resolved: 18/Aug/23

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

Type: Improvement Priority: Major - P3
Reporter: Brett Nawrocki Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-77638 Add logging on completion of resharding Closed
Assigned Teams:
Sharding NYC
Participants:

 Description   

Currently, resharding tracks metrics via ReshardingMetrics reported in $currentOp and ReshardingCumulativeMetrics (via its base class) reported in serverStatus. Because the serverStatus command returns metrics from the whole host in aggregate, it's difficult to capture metrics that are specific to a particular operation. As such, there are some metrics (e.g. duration spent in each phase) that are only reported by $currentOp. However, $currentOp is only available while the operation is still running, which limits its usefulness when trying to do analysis after the fact. Therefore, we should log the BSON object returned by reportForCurrentOp() at the end of the resharding operation.


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