[SERVER-67112] Create Resharding Cumulative Metrics Subclass Created: 08/Jun/22  Updated: 29/Oct/23  Resolved: 28/Jul/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: Brett Nawrocki
Resolution: Fixed Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-67108 Create Resharding Cumulative Metrics ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2022-07-11, Sharding 2022-07-25, Sharding 2022-08-08
Participants:

 Description   

Create a ReshardingCumulativeMetrics subclass of ShardingDataTransformCumulativeMetrics. All logic associated with tracking and reporting fields which are specific to be resharding should be moved into this new subclass from ShardingDataTransformCumulativeMetrics. The resharding specific cumulative fields are as follows:

  • oplogEntriesFetched
  • oplogEntriesApplied
  • insertsApplied
  • updatesAppied
  • deletesApplied
  • oplogFetchingTotalRemoteBatchRetrievalTimeMillis
  • oplogFetchingTotalRemoteBatchesRetrieved
  • oplogFetchingTotalLocalInsertTimeMillis
  • oplogFetchingTotalLocalInserts
  • oplogApplyingTotalLocalBatchRetrievalTimeMillis
  • oplogApplyingTotalLocalBatchesRetrieved
  • oplogApplyingTotalLocalBatchApplyTimeMillis
  • oplogApplyingTotalLocalBatchesApplied
  • All state field names (i.e. those in the section "currentInSteps")

This class should accept an instance of ReshardingCumulativeMetricsFieldNameProvider and use it while reporting its fields.



 Comments   
Comment by Githook User [ 28/Jul/22 ]

Author:

{'name': 'Brett Nawrocki', 'email': 'brett.nawrocki@mongodb.com', 'username': 'brettnawrocki'}

Message: SERVER-67112 Create ReshardingCumulativeMetrics subclass
Branch: master
https://github.com/mongodb/mongo/commit/b263fd5da80fe00213ccc8694f5215ab4da2159a

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