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 "Aaron T. Myers (JIRA)" <ji...@apache.org> on 2012/05/31 20:39:22 UTC
[jira] [Updated] (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
[ https://issues.apache.org/jira/browse/HDFS-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aaron T. Myers updated HDFS-3484:
---------------------------------
Attachment: HDFS-3484.patch
Here's a patch which addresses the issue. Determining the NN's info server now tries to use the configured HTTP address, but falls back on the configured NN RPC hostname + the configured HTTP port if the NN HTTP address is INADDR_ANY.
In addition to the included automated test, I've also tested this patch manually using fsck and verified that it correctly determines a resolve NN HTTP address when dfs.namenode.http-address is left at the default value.
> 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