hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-1464) Fix reporting of 2NN address when dfs.secondary.http.address is default (wildcard)
Date Tue, 19 Oct 2010 22:11:28 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Todd Lipcon updated HDFS-1464:
------------------------------

    Assignee: Todd Lipcon
      Status: Patch Available  (was: Open)

Simple patch that restores the pre-HDFS-1080 behavior for the case when the configured address
is wildcard.

No unit test included because this section of code is very difficult to isolate in a true
unit test (it uses static calls to TransferFsImage, etc), and in minicluster environments
the configs are all set properly.

> 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