[SERVER-64392] Achieve Feature Parity Between Existing and New Resharding Metrics Created: 09/Mar/22  Updated: 06/Dec/22  Resolved: 17/May/22

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

Type: Task Priority: Major - P3
Reporter: Brett Nawrocki Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Done Votes: 0
Labels: sharding-nyc-subteam1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-63623 Implemented Basic Global Index Metric... Closed
depends on SERVER-63634 Implemented Basic Global Index Metric... Closed
depends on SERVER-64370 Track and Report Parity All Role Fiel... Closed
depends on SERVER-64371 Implement Restoration for Parity All ... Closed
depends on SERVER-64372 Track and Report Parity Donor Fields ... Closed
depends on SERVER-64373 Implement Restoration for Parity Dono... Closed
depends on SERVER-64374 Track and Report Parity Recipient Cop... Closed
depends on SERVER-64375 Implement Restoration for Parity Reci... Closed
depends on SERVER-64376 Track and Report Parity Recipient App... Closed
depends on SERVER-64377 Implement Restoration for Recipient P... Closed
depends on SERVER-64384 Track and Report Parity Coordinator F... Closed
depends on SERVER-64385 Track and Report Parity Recipient Fie... Closed
is depended on by SERVER-64391 Adapt Existing ReshardingMetricsTest ... Closed
is depended on by SERVER-64393 Adapt ReshardingMetrics JavaScript Te... Closed
is depended on by SERVER-64394 Adapt Existing Test Uses of Reshardin... Closed
Assigned Teams:
Sharding NYC
Participants:
Generated at Thu Feb 08 06:00:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.