[
https://issues.apache.org/jira/browse/HDFS-4963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved HDFS-4963.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
1-win
Target Version/s: 1-win, 1.3.0
Hadoop Flags: Reviewed
+1 for the patch. Nice work, Arpit! I've committed this to branch-1 and
branch-1-win.
> Improve multihoming support in namenode
> ---------------------------------------
>
> Key: HDFS-4963
> URL: https://issues.apache.org/jira/browse/HDFS-4963
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 1.3.0
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
> Fix For: 1-win, 1.3.0
>
> Attachments: HDFS-4963.branch-1.001.patch,
> HDFS-4963.branch-1.002.patch, HDFS-4963.branch-1.patch
>
>
> HDFS does not work very well on multi-homed machines. A few open Jiras refer
> to this:
> # HDFS-1379
> # HADOOP-8198
> There are multiple issues involved here and some of them can be worked around
> by using alternate DNS names and configuring {{slave.host.name}} on Datanodes
> and task trackers.
> However namenode issues cannot be worked around because it does not respect
> the {{fs.default.name}} configuration. e.g. {{Namenode#initialize}} performs
> a gratuitous reverse DNS lookup to regenerate the hostname. Similar issues
> exist elsewhere.
> This Jira is being filed to fix some of the more serious problems. To avoid
> affecting existing users a new config setting may be introduced.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
