[SERVER-51777] Get rid of reduntant ShardRegistry::init function Created: 21/Oct/20  Updated: 09/Nov/20  Resolved: 09/Nov/20

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

Type: Improvement Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Won't Do Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Sharding 2020-11-02, Sharding 2020-11-16
Participants:

 Description   

The ShardRegistry is the only component living on the Grid that requires an additional initializing procedure after its creation. My claim is that this initializing procedure can be perform directly in the constructor. This will allow to simplify the logic of the ShardRegistry because it will eliminate one of its possible states:

  1. Created
  2. Initialized
  3. Up
  4. Shutdown
  5. Destructed

The shardRegistry creation happen respectively:



 Comments   
Comment by Tommaso Tocci [ 04/Nov/20 ]

I've put this temporarily in pause because it's not urgent and I've encountered a circular initialization dependency between the RSM and the ShardRegistry that prevent me to simply drop the ShardRegistry::init function.

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