hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3484) hdfs fsck doesn't work if NN HTTP address is set to 0.0.0.0 even if NN RPC address is configured
Date Thu, 31 May 2012 18:45:22 GMT

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

Eli Collins commented on HDFS-3484:
-----------------------------------

+1 looks good
                
> hdfs fsck doesn't work if NN HTTP address is set to 0.0.0.0 even if NN RPC address is
configured
> ------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-3484
>                 URL: https://issues.apache.org/jira/browse/HDFS-3484
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs client
>    Affects Versions: 2.0.0-alpha
>            Reporter: Aaron T. Myers
>            Assignee: Aaron T. Myers
>            Priority: Minor
>         Attachments: HDFS-3484.patch
>
>
> The default NN HTTP address is 0.0.0.0. Clients which need to connect to the HTTP address
(e.g. fsck and fetchImage) need an address which is actually resolvable, however. If the configured
NN HTTP address is set to 0.0.0.0, these clients should fall back on using the hostname configured
for the RPC address, with the port configured for the HTTP address.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message