[SERVER-3436] Allow for dynamic config of replset nodes to avoid reconfig when nodes' IP/name changes Created: 17/Jul/11  Updated: 12/Jul/16  Resolved: 11/Nov/11

Status: Closed
Project: Core Server
Component/s: Internal Code
Affects Version/s: 1.9.0
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Sridhar Nanjundeswaran Assignee: Dwight Merriman
Resolution: Done Votes: 1
Labels: azure, cloud
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Azure - The indiv nodes do not get fixed names or IPs


Issue Links:
Depends
Participants:

 Description   

If a node restarts in Azure it could come up with a different IP. In that case we need a way to designate this node as node "x" of the replset to avoid a reconfig. We need a way for the node to start as part of the replset, indicate it is node number "x", specify its IP as part of the startup/join and have the set dynamically reconfigure



 Comments   
Comment by Dwight Merriman [ 11/Nov/11 ]

doable now with the new

{cloud:...}

command which allows one to dynamically map logical names to ip:port endpoints.

Comment by Dwight Merriman [ 28/Sep/11 ]

what's the exact syntax we want for this command?

Generated at Thu Feb 08 03:03:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.