[ 
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12550869
 ] 

dhruba borthakur commented on HADOOP-2404:
------------------------------------------

I am unable to get it to working with this patch, I see this exception on all 
datanodes logs:

2007-12-12 07:15:14,063 ERROR org.apache.hadoop.dfs.DataNode: 
java.net.BindException: Address already in use
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at org.apache.hadoop.dfs.DataNode.startDataNode(DataNode.java:278)
        at org.apache.hadoop.dfs.DataNode.<init>(DataNode.java:204)
        at org.apache.hadoop.dfs.DataNode.makeInstance(DataNode.java:2204)
        at org.apache.hadoop.dfs.DataNode.run(DataNode.java:2148)
        at org.apache.hadoop.dfs.DataNode.createDataNode(DataNode.java:2169)
        at org.apache.hadoop.dfs.DataNode.main(DataNode.java:2360)

No message about "deprecated configuration parameter" appear in the datanode 
logs.

> HADOOP-2185 breaks compatibility with hadoop-0.15.0
> ---------------------------------------------------
>
>                 Key: HADOOP-2404
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2404
>             Project: Hadoop
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.16.0
>            Reporter: Arun C Murthy
>            Assignee: Konstantin Shvachko
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: ConfigurationConverter.patch
>
>
> HADOOP-2185 removed the following configuration parameters:
> {noformat}
> dfs.secondary.info.port
> dfs.datanode.port
> dfs.info.port
> mapred.job.tracker.info.port
> tasktracker.http.port
> {noformat}
> and changed the following configuration parameters:
> {noformat}
> dfs.secondary.info.bindAddress
> dfs.datanode.bindAddress
> dfs.info.bindAddress
> mapred.job.tracker.info.bindAddress
> mapred.task.tracker.report.bindAddress
> tasktracker.http.bindAddress
> {noformat}
> without a backward-compatibility story.
> Lots are applications/cluster-configurations are prone to fail hence, we need 
> a way to keep things working as-is for 0.16.0 and remove them for 0.17.0.

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

Reply via email to