You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2012/12/17 23:24:13 UTC

[jira] [Commented] (HDFS-4320) NameNode tries to get its address by looking at fs.default.name instead of its own config keys

    [ https://issues.apache.org/jira/browse/HDFS-4320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534377#comment-13534377 ] 

Hadoop QA commented on HDFS-4320:
---------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12561364/HDFS-4320.patch
  against trunk revision .

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3676//console

This message is automatically generated.
                
> NameNode tries to get its address by looking at fs.default.name instead of its own config keys
> ----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4320
>                 URL: https://issues.apache.org/jira/browse/HDFS-4320
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Mostafa Elhemali
>         Attachments: HDFS-4320.patch
>
>
> When NameNode starts up, it tries to find out its address by looking at the fs.default.name configuration key instead of using its own keys (namely dfs.namenode.servicerpc-address). This breaks scenarios where we try to configure a Hadoop cluster that uses a different default file system than DFS, but still try to prop up namenode and datanode services as a secondary file system.

--
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