[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563421#action_12563421
]
Hemanth Yamijala commented on HADOOP-2404:
------------------------------------------
bq. Sigh because of the reuse of mapred.task.tracker.report.bindAddress, which
conflicted with the meaning in 0.15, I needed a new name for that attribute.
All of the *.bindAddress's in 0.15 were of the form "0.0.0.0" and now we expect
"0.0.0.0:0", so it seemed better to give them a new extension. (Most of the
attributes changed prefixes in the bug that led to this one.) So, I changed the
attribute names to end with .address, which means that users can easily search
for problems in their configs.
Unfortunately, this change will break HOD. As I had noted earlier on in this
bug, HOD had not depended on backward compatibility, and had been coded to work
with Hadoop 0.16's names. Partly this was also because we needed to provide a
fix for our internal users who have been using HOD and Hadoop 0.16 trunk for a
long time now. HOD was also completely sync'ed up to Hadoop SVN yesterday a few
minutes before this change. So, we have two options as I see it:
- Try not to change the names that were originally proposed for Hadoop 0.16.
This is preferable for us.
- If for some reason we decide this is the right approach to take, we should
fix it as a blocker for HOD in the 0.16 release itself.
I would request we resolve this ASAP so we can make changes if necessary.
> 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.
