[SERVER-20282] Primary of shard replica set should update its connection string on the config servers on reconfig Created: 03/Sep/15 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
Currently any mongos or mongos process monitoring a shard replica set who notices a membership change in the set will attempt to update the config servers. This could lead to a lot of duplicate work. Instead the primary of the replica set being reconfigured should have sole responsibility for updating the config servers. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 03/Sep/15 ] |
|
As part of this when a shard mongod first becomes sharding aware it should also ensure the config servers have the correct connection string for it at that time. |