[SERVER-6083] Invalid replica set connection management Created: 13/Jun/12 Updated: 03/Jan/18 Resolved: 16/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.6 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker - P1 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Irrelevant |
||
| Operating System: | ALL |
| Participants: | |
| Case: | (copied to CRM) |
| Description |
|
When server already runs a MongoDB instance on default port and default (hostname-determined) IP address, initializing another instance with the same port but different IP address fails. This was very frustrating and I hope you will fix this soon. Also the message might disclose a little more information (for example what replica set name was encountered instead of the expected one). I think I've seen the case that was asking for that, but can't find this now. And while you're at it, please fix the "mongo host" vs "mongo host.zone" problem (if there are no dots in name, shell always tries local host instead of host, relative to search order, specified in resolv.conf), I think it's the same problem. |
| Comments |
| Comment by Aristarkh Zagorodnikov [ 15/Sep/12 ] |
|
We scrapped all these machines already and moved to VMs that have unique network interfaces, so it's no longer a problem. |
| Comment by Eliot Horowitz (Inactive) [ 15/Sep/12 ] |
|
I don't think that's what happened. |
| Comment by Aristarkh Zagorodnikov [ 13/Jun/12 ] |
|
Also, the following line when port is changed right after initiation indicates that it really tries to connect to localhost: |