[
https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699677#action_12699677
]
Andrey Kuzmin commented on HADOOP-5670:
---------------------------------------
Couple of suggestions (assuming zookeeper option) based on past experience with
similar issue.
1. Splitting configuration into two parts - default and site-specific overrides
(with further specialization down the line) - would simplify hadoop upgrade by
minimizing upgrade impact on locally overridden options.
2. If zookeeper does not provide for node-local persistent caching, adding this
option specifically for configuration data could support disconnected node
operations if need be (say, for sanity checks on start-up).
> Hadoop configurations should be read from a distributed system
> --------------------------------------------------------------
>
> Key: HADOOP-5670
> URL: https://issues.apache.org/jira/browse/HADOOP-5670
> Project: Hadoop Core
> Issue Type: New Feature
> Components: conf
> Reporter: Allen Wittenauer
>
> Rather than distributing the hadoop configuration files to every data node,
> compute node, etc, Hadoop should be able to read configuration information
> (dynamically!) from LDAP, ZooKeeper, whatever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
