[
https://issues.apache.org/jira/browse/HDFS-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791222#action_12791222
]
Tom White commented on HDFS-367:
--------------------------------
Having this property would make it more obvious that the namenode can be
configured to bind to multiple network interfaces (by setting
dfs.namenode.address to 0.0.0.0:8020), bringing it in line with other daemons
like the datanodes and tasktrackers (and the web interfaces). The problem of
binding to the wrong interface crops up quite a lot on the user list (e.g.
http://markmail.org/message/ew6mg4exzsc3kqcy).
> Make HDFS daemons independent of fs.default.name
> ------------------------------------------------
>
> Key: HDFS-367
> URL: https://issues.apache.org/jira/browse/HDFS-367
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Tom White
>
> Having the HDFS daemons get the namenode host and port from the
> fs.default.name property makes less sense in a world with multiple
> filesystems. This is confusing to users, so a new property to define the
> namenode host and port should be introduced.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
