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 "Harsh J (Resolved) (JIRA)" <ji...@apache.org> on 2011/12/29 13:27:30 UTC
[jira] [Resolved] (HDFS-36) Handling of deprecated
dfs.info.bindAddress and dfs.info.port
[ https://issues.apache.org/jira/browse/HDFS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J resolved HDFS-36.
-------------------------
Resolution: Cannot Reproduce
Can't reproduce on 1.0+. Setting dfs.http(s).address suffices.
> Handling of deprecated dfs.info.bindAddress and dfs.info.port
> -------------------------------------------------------------
>
> Key: HDFS-36
> URL: https://issues.apache.org/jira/browse/HDFS-36
> Project: Hadoop HDFS
> Issue Type: Bug
> Environment: Windows XP
> Reporter: Cagdas Gerede
> Priority: Minor
>
> When checkpointing is triggered in Secondary name node, Secondary name node throws exception while it tries to connect to Namenode's http server in the following two cases:
> 1) In hadoop-site.xml, if you put only dfs.http.address but not dfs.info.bindAddress and dfs.info.port (Connection Refused Exception)
> 2) In hadoop-site.xml, if you put only dfs.info.bindAddress and dfs.info.port but not dfs.http.address (SecondaryNameNode.getServerAddress line 148 throws exception since newAddrPort is null)
> Temporary Solution: If you put dfs.http.address, dfs.info.bindAddress, and dfs.info.port, then SecondaryNameNode successfully fetches the image and log from Namenode.
--
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