[SERVER-24072] config server should persistently store it's own name Created: 05/May/16 Updated: 06/Dec/22 Resolved: 06/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.3.5 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Participants: | |||||||||
| Description |
|
that is recognized by the sharded cluster. This is so that it will be able to send to the shards the "config server connection" string the shards can use to talk to it. |
| Comments |
| Comment by Randolph Tan [ 06/May/16 ] |
|
Yeah, now that you mention it, config servers can only be replica sets. Closing ticket |
| Comment by Spencer Brody (Inactive) [ 05/May/16 ] |
|
Should it just be fetching this information from the replica set config? |