[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553565
]
Konstantin Shvachko commented on HADOOP-2404:
---------------------------------------------
We are not converging here. Your arguments are mostly about how the
configuration should be structured.
Doug, you are trying to kill two birds with this one:
- provide compatibility and
- clean up the configuration mess.
I prefer to keep them separate and just concentrate on the compatibility.
Because as this issue reveals
common ground on the general configuration issue will be harder to achieve.
> I also have misgivings about mutating the configuration. Won't that confuse
> folks?
Interesting point. If somebody uses the default configuration and expects to be
able to
obtain a non-existing parameter, like "dfs.info.port" from it in some legacy
code it will fail.
And there isn't much you can do about it.
That is another reason for declaring this an incompatible change.
To summarize the above we have 4 proposals:
# Declare the port patch an incompatible change and ask people to change their
configurations.
# Accept current conversion patch with all changes localized in one class, and
revert it after release 0.16.
Although the practice of making application-specific changes in
Configuration.java is a bad practice.
# Provide static configuration parameter getters (and setters?) related to each
component and call
them consistently within the code.
# Create a separate class ConfigurationConverter (packaged in hadoop.util?)
with a deprecated
static method for conversion, and call the method in NameNode, DataNode,
JobTracker, TaskTracker,
SeondaryNamenode, and DFSClient constructors.
I am in favor of 1, but I am ok with 2 and 4.
> 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.
