[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563820#action_12563820
]
Hemanth Yamijala commented on HADOOP-2404:
------------------------------------------
bq. Could HOD take out the branches that were added to support HADOOP-2185?
Since after the current patch, the pre-2185 configuration will work again...
that seems like a pretty easy solution for now. Thoughts?
We thought about this. It is actually easier to just change the names of the
variables. This is just a string replacement in code, and is a pretty harmless
change. Also, thinking longer term, we would rather work with Hadoop 0.16 by
default, rather than earlier versions. That way, if this change is deprecated
and removed in the next release, we could just knock out the deprecated Hadoop
0.15 configuration from HOD.
That said, both methods will involve making changes in HOD
If it helps in making a decision, I repeat my opinion:
- Preferred choice, do not use the new names.
- Next choice: if the Hadoop community feels this change is good, we will make
the changes in HOD to sync up. No problems with that. We require very little
time to make the changes.
IOW, please make a decision and we'll follow. *smile*
> 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: 2404.patch, 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.
