[SERVER-57156] Separate resharding metrics into separate classes for coordinator/donor/recipient Created: 24/May/21  Updated: 07/Feb/22  Resolved: 07/Feb/22

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

Type: Improvement Priority: Major - P3
Reporter: Blake Oler Assignee: Lamont Nelson
Resolution: Won't Do Votes: 1
Labels: PM-234, PM-234-T-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backport Requested:
v5.0
Sprint: Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09, Sharding 2021-08-23, Sharding 2021-09-06, Sharding 2021-09-20, Sharding 2021-10-04, Sharding 2021-10-18, Sharding 2021-11-01, Sharding 2021-11-15, Sharding 2021-11-29, Sharding 2021-12-13, Sharding 2021-12-27, Sharding 2022-01-10, Sharding 2022-01-24, Sharding 2022-02-07
Participants:

 Description   

The current resharding metrics design doesn't align with how state machines are modeled. It will be cleaner and easier to maintain in the future to separate into three classes sub-classes from a metrics interface.


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