[SERVER-24057] Remove ShardRegistry::createConnection in favor of creating a RemoteCommandTargeter directly Created: 04/May/16 Updated: 06/Dec/22 Resolved: 05/Dec/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: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | PM550 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
ShardRegistry::createConnection is used during addShard to create a detached Shard object corresponding to the servers we are in the process of trying to add. We use it only to get the RemoteCommandTargeter off it. We should instead just make a RemoteCommandTargeter directly, and no longer be in the business of having Shard objects for servers that aren't yet actually shards |
| Comments |
| Comment by Andy Schwerin [ 05/Dec/16 ] |
|
Good idea, but not a priority right now. |