Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-33883

Implement fallback from IPv6 to IPv4 on outgoing connections

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Won't Fix
    • None
    • None
    • Networking
    • Service Arch
    • 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

    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.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33790 Mongos v3.7.2-387 fails to connect to config server at startup on Windows and Mac

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-33371 Don't allocate resources for ingress connection until first byte is received

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-39185 Connect to IPv4 and IPv6 in parallel for outgoing connections

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-servicearch Backlog - Service Architecture
              shane.harvey@mongodb.com Shane Harvey
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: