[
https://issues.apache.org/jira/browse/HADOOP-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553484
]
Doug Cutting commented on HADOOP-2404:
--------------------------------------
> I'd prefer to have a separate configuration class per component combining its
> configuration logic rather than having static methods all around, but I'd
> rather continue this discussion in the other issue.
I agree that configuration should be per-component. But in this case, each
component already has a well-known primary class: Namenode, Datanode,
JobTracker, TaskTracker, etc. Or would you rather partition things into simply
mapred and hdfs? Personally, I don't think of those as components so much as
sub-systems, and think that those existing classes are appropriate for these
accessors long-term. If you don't agree, then I guess we'll have to push this
to another issue.
I also have misgivings about mutating the configuration. That can make things
trickier to debug, since the values in the configuration that are displayed
won't match those that the user passed. Won't that confuse folks?
It would indeed be nice to have the back-compatibility code in a single place
that can easily be deprecated, but we could instead add a consistent comment to
each of these places, and file an issue now to remove all places that are
so-commented.
> 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.
