[SERVER-64385] Track and Report Parity Recipient Fields in ServerStatus Created: 09/Mar/22  Updated: 29/Oct/23  Resolved: 05/May/22

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

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 2022-05-02, Sharding NYC 2022-05-16
Participants:
Story Points: 3

 Description   

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

  • oplogEntriesApplied
  • oplogEntriesFetched
  • collectionCloningTotalRemoteBatchRetrievalTimeMillis
  • collectionCloningTotalRemoteBatchesRetrieved
  • oplogApplyingTotalLocalBatchApplyTimeMillis
  • oplogApplyingTotalLocalBatchesApplied
  • insertsApplied
  • updatesApplied
  • deletesApplied
  • documentsProcessed
  • bytesWritten


 Comments   
Comment by Githook User [ 05/May/22 ]

Author:

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

Message: SERVER-64385 Track and Report Parity Recipient Fields in ServerStatus
Branch: master
https://github.com/mongodb/mongo/commit/2f2dd5d7e1182eee439b4cd67f1a299513a7aca3

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