[
https://issues.apache.org/jira/browse/HDFS-8271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14529197#comment-14529197
]
Colin Patrick McCabe commented on HDFS-8271:
--------------------------------------------
An uber jira is a good idea. Also, let's not change default behavior by
binding on ipv6 by default. It will create problems for sure.
> NameNode should bind on both IPv6 and IPv4 if running on dual-stack machine
> and IPv6 enabled
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-8271
> URL: https://issues.apache.org/jira/browse/HDFS-8271
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 2.7.1
> Reporter: Nate Edel
> Assignee: 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)
