[DOCS-35] Private IP and private hostnames vs Elastic IP and public hostname configuration in Amazon Ec2 Created: 29/Sep/10  Updated: 29/Nov/12  Resolved: 29/Sep/10

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Robert Ford Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 13 years, 21 weeks ago

 Description   

Some parts of mongodb seem to be sensitive to IP's vs hostnames when it comes to using config servers. I was wondering if you had a best practice of what set of IPs/hostnames we should use when configuring mongodb. For example :

replSet configurations such as rs.add() or adding members to the config. rs.initiate() always uses the private hostname for the first server but we could create the config manually and then initialize with that if public hostnames are the way to go.
configsvr configurations such as db.runCommand(

{ addshard : "replsetname/<private or public hostname>:port"}

)
mongos --configdb <private ip, private hostname, elastic ip, or public hostname>:port,,...

I would like to make sure we are using the right settings for all of this while in the cloud.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 29/Sep/10 ]

Doesn't much matter though - there are pros and cons of both

Comment by Eliot Horowitz (Inactive) [ 29/Sep/10 ]

Generally its better to use internal ips or external hostnames, as those will resolve to the local ips from inside.

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