[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-2404:
----------------------------------
Attachment: 2404.patch
Ok, I made a specific (and deprecated) method in to
org.apache.hadoop.net.NetUtils that gets the old bind address attribute name.
*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. In particular, the names are now:
dfs.secondary.http.bindAddress -> dfs.secondary.http.address
dfs.datanode.bindAddress -> dfs.datanode.address
dfs.datanode.http.bindAddress -> dfs.datanode.http.address
dfs.http.bindAddress -> dfs.http.address
mapred.job.tracker.http.bindAddress -> mapred.job.tracker.http.address
mapred.task.tracker.report.bindAddress -> mapred.task.tracker.report.address
mapred.task.tracker.http.bindAddress -> mapred.task.tracker.http.address
> 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.
