[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: |
|
||||||||
| Sprint: | Sharding 13 (04/22/16), Sharding 14 (05/13/16) | ||||||||
| Participants: | |||||||||
| Description |
|
In order to complete 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 |
| 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. |