hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2404) HADOOP-2185 breaks compatibility with hadoop-0.15.0
Date Fri, 28 Dec 2007 23:30:43 GMT

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

Konstantin Shvachko updated HADOOP-2404:
----------------------------------------

    Attachment: ConfigConvert2.patch

Yes, the old code was setting (by mistake I am sure) "mapred.task.tracker.report.address"
instead of "...bindAddress".
The former is a non-existing configuration parameter, setting of which to anything would not
cause any problems since 
it is not used anywhere. But I agree fixing one bug does not release you from the responsibility
of fixing another one
in the same line. Here is the patch that takes care of this problem.

> 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: ConfigConvert.patch, ConfigConvert2.patch, 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.


Mime
View raw message