Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <12626460.1198095284154.JavaMail.jira@brutus>
Date: Wed, 19 Dec 2007 12:14:44 -0800 (PST)
From: "Konstantin Shvachko (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-2404) HADOOP-2185 breaks compatibility
 with hadoop-0.15.0
In-Reply-To: <22781223.1197372523409.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------

> It's a good idea to always access parameters through accessor methods. 

Nobody is arguing with that, but this is not a part of this issue.

I like Dhruba's proposal better. It will still change several files, but definitely less than 27.

> 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.