[SERVER-11128] Warn about configurations involving IP addresses. Created: 11/Oct/13 Updated: 06/Dec/22 Resolved: 06/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | 0.9.3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Richard Kreuter (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | validation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
One way that people end up with problems is configuring a replica set or sharded cluster using IP addresses (especially EC2 ip-10-blahblah addresses, which can go away at unpredictable moments). Would be nice if we warned about that at startup and/or elsewhen, linked to docs about how to correct it afterward. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 06/Sep/18 ] |
|
alyson.cabral will follow up with the Cloud team to see if they have a warning like this (or should) |
| Comment by Henrik Ingo (Inactive) [ 14/Aug/14 ] |
|
richard@10gen.com Can you clarify what are you talking about in this ticket? Is this about using a transient address/hostname for the config servers (which does lead to problems), or using AWS internal addresses at all (in which case I don't understand what the problem is)? |