[SERVER-64384] Track and Report Parity Coordinator Fields in ServerStatus Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 19/Apr/22

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

Type: New Feature Priority: Major - P3
Reporter: Brett Nawrocki Assignee: Randolph Tan
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-64392 Achieve Feature Parity Between Existi... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2022-04-18, Sharding 2022-05-02
Participants:
Story Points: 2

 Description   

Add members to ShardingDataTransformCumulativeMetrics to track the below coordinator fields necessary for achieving parity with existing metrics. These fields should also be reported when serializing the ServerStatus report.

  • countStarted
  • countSucceeded
  • countFailed
  • countCanceled
  • coordinatorAllShardsLowestRemainingOperationTimeEstimatedMillis
  • coordinatorAllShardsHighestRemainingOperationTimeEstimatedMillis
  • lastOpEndingChunkImbalance


 Comments   
Comment by Githook User [ 19/Apr/22 ]

Author:

{'name': 'Randolph Tan', 'email': 'randolph@10gen.com', 'username': 'renctan'}

Message: SERVER-64384 Track and Report Parity Coordinator Fields in ServerStatus
Branch: master
https://github.com/mongodb/mongo/commit/572cb2ea4d872432ce95c0de1c5cf4d37641b50a

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