[SERVER-2195] Change names/ips of members Created: 09/Dec/10 Updated: 06/Dec/22 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | features we're not sure of |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (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 |
|
Add the ability to change the names/ips for members. In the case that you have a total failure in ec2 when things come back up they will have new ips (and names). |
| Comments |
| Comment by Remon van Vliet [ 12/Oct/11 ] | |
|
I've added this to a few JIRA issues by now; idiot proofing is NOT the way to go. DNS based solutions aren't always practical nor does the lack of this feature help automating up/downscaling of our various mongo clusters. MongoDB should offer a full suite of cluster management tools. That it can be dangerous to use such a feature cannot be a reason not to add it. | |
| Comment by Michael Schurter [ 12/Oct/11 ] | |
|
Does this mean you can't change shard members at all? One of my shards improperly picked up an old decommissioned member of a replica set and now periodically logs:
Where proc04:27017 was a temporary member of set01 but removed via rs.remove("proc04:27017") (before even adding the shard iirc... confused how the shard picked it up). At any rate, while dangerous, being able to manipulate shard members seems crucial for fixing misconfigurations or mitigating unforeseen bugs in mongos/configsvr. | |
| Comment by Eliot Horowitz (Inactive) [ 09/Dec/10 ] | |
|
We've generally been opposed to this as it makes it very easy to screw things up. |