[SERVER-33883] Implement fallback from IPv6 to IPv4 on outgoing connections Created: 14/Mar/18  Updated: 06/Dec/22  Resolved: 24/Jan/19

Status: Closed
Project: Core Server
Component/s: Networking
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Shane Harvey Assignee: Backlog - Service Architecture
Resolution: Won't Fix Votes: 0
Labels: service_architecture
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-33790 Mongos v3.7.2-387 fails to connect to... Closed
related to SERVER-33371 Don't allocate resources for ingress ... Closed
related to SERVER-39185 Connect to IPv4 and IPv6 in parallel ... Closed
Assigned Teams:
Service Arch
Sprint: Service Arch 2018-10-08, Service Arch 2018-10-22, Service Arch 2018-11-05, Service Arch 2018-11-19, Service Arch 2019-01-28
Participants:

 Description   

From SERVER-33790, it's my understanding that a server started with --ipv6 only resolves hostnames to IPv6 address(es) for outgoing connections. Instead, the server could use the hostname's IPv4 address(es) as a fallback when the IPv6 connection attempt fails.



 Comments   
Comment by Gregory McKeon (Inactive) [ 24/Jan/19 ]

shane.harvey linked.

Comment by Shane Harvey [ 24/Jan/19 ]

greg.mckeon can you link the ticket where the server will implement connecting to IPv6 and v4 in parallel for outgoing connections?

Comment by Gregory McKeon (Inactive) [ 24/Jan/19 ]

Given that Drivers has found a workaround for the linked ticket, we feel that the full solution of "Happy Eyeballs" (connecting to IPv6 and v4 in parallel) would be better than doing this ticket as described.

Comment by Jonathan Ma [ 24/Jan/19 ]

The repro given in SERVER-33790 doesn't seem to be reproducible on 3.7 or 4.0

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