hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2404) HADOOP-2185 breaks compatibility with hadoop-0.15.0
Date Fri, 25 Jan 2008 04:52:37 GMT

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

Owen O'Malley updated HADOOP-2404:
----------------------------------

    Assignee: Owen O'Malley  (was: Konstantin Shvachko)
      Status: Open  (was: Patch Available)

1. The method as proposed isn't general enough to be useful to more than this context.
2. It does not handle the case where the port or just the bind address are defined in the
old style, but not the other.
3. It will always generate a warning about the task tracker, since the old value was set by
the code.
4. The task tracker report bind address changed syntax without changing configuration names.
5. The configuration now lets users define non-zero ports for the task tracker server.

Since Konst is sick, I'll roll a new patch.

> HADOOP-2185 breaks compatibility with hadoop-0.15.0
> ---------------------------------------------------
>
>                 Key: HADOOP-2404
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2404
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.16.0
>            Reporter: Arun C Murthy
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.16.0
>
>         Attachments: ConfigConvert.patch, ConfigConvert2.patch, ConfigConvert3.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