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 "Tom White (JIRA)" <ji...@apache.org> on 2008/07/17 20:51:33 UTC

[jira] Commented: (HADOOP-3782) Make HDFS daemons independent of fs.default.name

    [ https://issues.apache.org/jira/browse/HADOOP-3782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614486#action_12614486 ] 

Tom White commented on HADOOP-3782:
-----------------------------------

Implementation note from Doug: "For back-compatibility we could leave it empty by default, deferring to fs.default.name, only if folks specify a non-empty dfs.namenode.address would it be used."

> Make HDFS daemons independent of fs.default.name
> ------------------------------------------------
>
>                 Key: HADOOP-3782
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3782
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            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.