[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563305#action_12563305
]
Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------
Reviewing code per Owen's request.
# I am not sure changing names again is such a good idea. Are we going to need
a backward compatibility for this new change too?
# I am getting NPE if I run with the old configuration.
{code}
08/01/28 21:28:48 ERROR dfs.NameNode: java.lang.NullPointerException
at org.apache.hadoop.net.NetUtils.getServerAddress(NetUtils.java:131)
at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:279)
at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
{code}
Basically this code does not work if newBindAddressName is not present.
# For task tracker "mapred.task.tracker.report.port" property never existed. So
the oldPort will remain unitialized.
# What happend with the default values? Don't we need them?
# I don't see how this is different from the previous approaches, and why we
are spending so many resources on such an insignificant issue.
> 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.
