Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Won't Fix
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Networking
Labels:
- service_architecture

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
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

related to

SERVER-33790 Mongos v3.7.2-387 fails to connect to config server at startup on Windows and Mac

Closed

SERVER-33371 Don't allocate resources for ingress connection until first byte is received

Closed

SERVER-39185 Connect to IPv4 and IPv6 in parallel for outgoing connections

Closed

Assignee:: [DO NOT USE] Backlog - Service Architecture
Reporter:: Shane Harvey
Participants:: [DO NOT USE] Backlog - Service Architecture, Gregory McKeon, Jonathan Ma, Shane Harvey
Votes:: 0 Vote for this issue
Watchers:: 5 Start watching this issue

Created:: Mar 14 2018 06:01:45 PM UTC
Updated:: Dec 06 2022 03:35:19 AM UTC
Resolved:: Jan 24 2019 08:09:07 PM UTC
Confidence Status Last Update:: 23/Jan/19 5:02 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates