You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Elliott Clark (JIRA)" <ji...@apache.org> on 2015/12/23 01:37:46 UTC

[jira] [Resolved] (HADOOP-12431) NameNode should bind on both IPv6 and IPv4 if running on dual-stack machine and IPv6 enabled

     [ https://issues.apache.org/jira/browse/HADOOP-12431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliott Clark resolved HADOOP-12431.
------------------------------------
    Resolution: Won't Fix
      Assignee:     (was: Nemanja Matkovic)

Going to resolve this one as won't fix. We don't want to bind to ipv6 by default. Instead I'm going to open a documentation jira about how to set up a cluster with dual stack.

> NameNode should bind on both IPv6 and IPv4 if running on dual-stack machine and IPv6 enabled
> --------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-12431
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12431
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: 2.7.1
>            Reporter: Nate Edel
>              Labels: ipv6
>
> NameNode works properly on IPv4 or IPv6 single stack (assuming in the latter case that scripts have been changed to disable preferIPv4Stack, and dependent on the client/data node fix in HDFS-8078).  On dual-stack machines, NameNode listens only on IPv4 (even ignoring preferIPv6Addresses being set.)
> Our initial use case for IPv6 is IPv6-only clusters, but ideally we'd support binding to both the IPv4 and IPv6 machine addresses so that we can support heterogenous clusters (some dual-stack and some IPv6-only machines.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)