[SERVER-69954] ShardingDataTransformCumulativeMetrics Does Not Report Oldest Operation's Elapsed Time Created: 23/Sep/22 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brett Nawrocki | Assignee: | Backlog - Cluster Scalability |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cs-subteam1, sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Cluster Scalability
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Story Points: | 2 | ||||||||
| Description |
|
We currently document a serverStatus field shardingStatistics.resharding.totalOperationTimeElapsedMillis, however this field was never actually reported by the old metrics implementation as of 6.0 and is also not reported by the new implementation which we started using in 6.1. The oldest running resharding operation's elapsed time in milliseconds should be reported in the output of serverStatus as shardingStatistics.resharding.oldestActive.totalOperationTimeElapsedMillis. Consider also adding a counter for the elapsed time for the most recent successful operation, to ease tracking resharding performance in atlas based on historical serverStatus data. |