[SERVER-64385] Track and Report Parity Recipient Fields in ServerStatus - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: New Feature
Status: Closed
Priority: Major - P3
Resolution: Fixed
Affects Version/s: None
Fix Version/s: 6.0.0-rc5
Component/s: Sharding
Labels:
- sharding-nyc-subteam1

Backwards Compatibility:
Fully Compatible
Sprint:
Sharding 2022-05-02, Sharding NYC 2022-05-16
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

Attachments

Issue Links

is depended on by

SERVER-64392 Achieve Feature Parity Between Existing and New Resharding Metrics

Closed

Activity

People

Assignee:: Randolph Tan

Reporter:: Brett Nawrocki

Participants:: Brett Nawrocki, Githook User, Randolph Tan

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Dates

Created:: Mar 09 2022 08:15:44 PM UTC

Updated:: May 05 2022 02:36:07 PM UTC

Resolved:: May 05 2022 02:36:07 PM UTC