[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551099
]
Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------
Dhruba, this means that there is something else running on the same port. Most
likely another data-node on the default port.
As I mentioned before this patch does not reverse port rolling behavior, just
provides support for the deprecated config parameters.
And "deprecated configuration parameter" message does not appear because your
configuration does not contain old names.
The application you use should explicitly specify port 0 if the actual port #
is meant to be arbitrary.
Doug, I agree this would be a better solution. But this will be a much bigger
change now and then when we remove
deprecation. There are 5 servers involved. So at least 5 places should be
patched if we go your way.
The problem is only with HOD for now as I understand. HOD does not use
Configuration class, but rather
generates xml files by directly writing into them. So there is no way they can
call any methods at all.
> 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.
