[SERVER-64374] Track and Report Parity Recipient Copying Fields in CurrentOp 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: 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
is depended on by SERVER-64375 Implement Restoration for Parity Reci... Closed
is depended on by SERVER-64392 Achieve Feature Parity Between Existi... Closed
Duplicate
is duplicated by SERVER-57094 Plumb through duration timestamps in ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2022-04-04, Sharding NYC 2022-04-18, Sharding 2022-05-02
Participants:
Story Points: 3

 Description   

Add members to ShardingDataTransformInstanceMetrics to track the below recipient-only fields necessary to achieve parity with the existing metrics. These fields should also be reported when serializing the CurrentOp report.

Fields:

  • approxDocumentsToCopy
  • documentsCopied
  • approxBytesToCopy
  • bytesCopied
  • totalCopyTimeElapsedSecs (will require adding a new, optional field to the RecipientStateMachine)


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

Author:

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

Message: SERVER-64374 Add parity $currentOp resharding recipient copying fields
Branch: master
https://github.com/mongodb/mongo/commit/a20861fbbdc72e721879da9a47a77887255dbcf7

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