[SERVER-23139] ShardRegistry on config servers should read the registry information from local storage Created: 14/Mar/16  Updated: 10/May/16  Resolved: 10/May/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Duplicate Votes: 0
Labels: shardregistry
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-23120 Make ShardRegistry available for use ... Closed
Sprint: Sharding 13 (04/22/16), Sharding 14 (05/13/16)
Participants:

 Description   

In order to complete SERVER-23120 as quick as possible and unblock other work that depended on it, we installed a ShardRegistry on the config servers that works the same as the ShardRegistry running on shards or mongoses. This means then whenever it needs to reload information about the membership in the cluster, it makes a network connection to a config server (possibly this very same node), rather than just reading the contents of the config.shards collection from the local storage engine.

This should be cleaned up as part of the upcoming ShardRegistry refactoring work.



 Comments   
Comment by Spencer Brody (Inactive) [ 10/May/16 ]

Description of this ticket is wrong. We never did the half-measure fix for SERVER-23120, we just waited and got it fully working and properly reading from local storage. This ticket is now essentially a duplicate of SERVER-23120

Comment by Spencer Brody (Inactive) [ 14/Mar/16 ]

As part of this we should also consider making the ShardRegistry a decoration on ServiceContext so that we can provide a ShardRegistry on the config servers without needing to initialize the 'grid' or 'ShardingState' objects.

Generated at Thu Feb 08 04:02:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.