[SERVER-65817] Simplify initialization of BalancerStatsRegistry Created: 20/Apr/22  Updated: 01/Jun/23  Resolved: 01/Jun/23

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-65815 Remove OrphanTracking feature flag Closed
Related
related to SERVER-77714 Complete TODO listed in SERVER-65817 Closed
Assigned Teams:
Sharding EMEA
Participants:

 Description   

Currently the BalancerStatsRegistry can only be used on FCV in which the OrphanTracking feature flag is enabled (>= 6.0).
For this reason the initialization/termination logic of the registry is a bit convoluted.

Once the OrphanTracking feature flag is removed ( SERVER-65815) we should simplify the logic by assuming that the registry is only initialized on stepUp and terminated on stepDown.

This means that we can stop exposing BalancerStatsRegistry::initializeAsync and BalancerStatsRegistry::terminate functions


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