[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557109#action_12557109
]
Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------
It sounds like you are under the impression that the original patch was just
about renaming a bunch of configuration parameters.
It was not. It was about prohibiting port rolling. This is a security issue.
Security changes are always like that: people are irritated when you impose
more restrictions on them.
And it is an incompatible change in its nature. What is the point of
restricting if you let everybody go around it?
Suppose that I left all the parameters unchanged, then people would have had
hard (even harder) time understanding what is going wrong with their code.
That is why I thought it was appropriate to change names at the same time the
semantics of the parameter was changing.
I thought and still think it is more fair not to provide any backward
compatibility at all in this case rather than to provide partial compatibility
in the form of old name recognition.
Will not repeat all the arguments again, but it looks like they convinced
Hemanth, and turned Arun into willing-to-listen state.
I understand your irritation on the configuration issues, but I don't
understand why blame my or equally any other patch for not dealing with them.
I do not favor the idea of creating static getters for configuration parameters
in NameNode, TaskTracker etc. classes. Just commented on that in HADOOP-2385.
> 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: ConfigConvert.patch, ConfigConvert2.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.
