hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1464) Fix reporting of 2NN address when dfs.secondary.http.address is default (wildcard)
Date Wed, 22 Dec 2010 00:56:01 GMT

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

Hadoop QA commented on HDFS-1464:
---------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12457612/hdfs-1464.txt
  against trunk revision 1051669.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: https://hudson.apache.org/hudson/job/PreCommit-HDFS-Build/19//console

This message is automatically generated.

> Fix reporting of 2NN address when dfs.secondary.http.address is default (wildcard)
> ----------------------------------------------------------------------------------
>
>                 Key: HDFS-1464
>                 URL: https://issues.apache.org/jira/browse/HDFS-1464
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: name-node
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: hdfs-1464.txt
>
>
> HDFS-1080 broke the way that the 2NN identifies its own hostname to the NN during checkpoint
upload. It used to use the local hostname, which as HDFS-1080 pointed out was error prone
if it had multiple interfaces, etc. But now, with the default setting of dfs.secondary.http.address,
the 2NN reports "0.0.0.0", which won't work either.
> We should look for the wildcard bind address and use the local hostname in that case,
like we used to.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message