[SERVER-33790] Mongos v3.7.2-387 fails to connect to config server at startup on Windows and Mac Created: 09/Mar/18 Updated: 23/Apr/18 Resolved: 14/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shane Harvey | Assignee: | Jonathan Reams |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
It appears that mongos cannot connect to config server replica set when mongo-orchestration is starting a sharded cluster without authentication and without SSL. I can also reproduce this locally on Mac with mongodb version:
This is the sequence of events:
Here's mongos failing to connect to the config server with a log level 5:
For more info see https://github.com/10gen/mongo-orchestration/issues/239 |
| Comments |
| Comment by Jonathan Reams [ 14/Mar/18 ] | |||||||||
|
We've decided not to fix this since the old behavior depended on some hard-coded hostname resolution rules ("localhost" always resolved to "127.0.0.1" no matter what) that we'd prefer not to carry forward. The two tickets to improve current behavior have been opened and are linked to this ticket. | |||||||||
| Comment by Shane Harvey [ 14/Mar/18 ] | |||||||||
|
This issue is actually a bug in mongo-orchestration's sharded cluster setup. It unintentionally starts a config server without --ipv6 when the rest of the nodes in the cluster have --ipv6. I do have two requests:
| |||||||||
| Comment by Jonathan Reams [ 13/Mar/18 ] | |||||||||
|
The issue is that the old egress networking code always resolved localhost to 127.0.0.1. This behavior dates back to the 1.8 days. This is pretty straightforward to fix, but this "fixed" behavior feels very strange to me. | |||||||||
| Comment by Bernie Hackett [ 13/Mar/18 ] | |||||||||
|
Is the issue that when mongos is started with --ipv6 mongod also now has to be started with --ipv6? If mongod had been started with --ipv6 would we never have seen this bug? | |||||||||
| Comment by Shane Harvey [ 12/Mar/18 ] | |||||||||
|
Again this is on both Windows and Mac OS with the latest build of the server:
| |||||||||
| Comment by Shane Harvey [ 12/Mar/18 ] | |||||||||
|
In the search for a repro without using MO I believe I've found the issue. Mongos cannot connect when started with the --ipv6 flag.
| |||||||||
| Comment by Mark Benvenuto [ 12/Mar/18 ] | |||||||||
|
Do you have a repro without mongo-orchestration? If the best way is use mongo-orchestration:
|