[SERVER-26123] initial ShardRegistry reload done twice Created: 15/Sep/16 Updated: 11/Jan/17 Resolved: 11/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2017-01-02 | ||||||||
| Participants: | |||||||||
| Description |
|
It looks like the initial reloading of the shard registry is done in two places: 1) ShardRegistry::startup() 2) reloadShardRegistryUntilSuccess() We may want to have it just done in one place. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 11/Jan/17 ] |
|
reloadShardRegistryUntilSuccess() does not reload the shard registry, despite its name. |