[
https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854023#action_12854023
]
Allen Wittenauer commented on HADOOP-5670:
------------------------------------------
Considering that the task tracker talks to the job tracker (where the scheduler
runs), the dynamic add/join is already there.
I want to re-iterate something here: Think about the client, not just the
server! Chances are good the clients are NOT owned by the same entity that
runs the Hadoop grid. Building something that is strictly usable by the server
is not going to be that much in terms of bang-for-the-buck, considering any
reasonable configuration management tool could do that.
... and given the various private convos I've had about this, I'm still not
convinced ZK is a reasonable answer. Sure you can probably do more with it,
but that comes at a cost, especially on the operations side where there is
(highly likely) already a DS in place. It just isn't practical to require ZK
for this.
> Hadoop configurations should be read from a distributed system
> --------------------------------------------------------------
>
> Key: HADOOP-5670
> URL: https://issues.apache.org/jira/browse/HADOOP-5670
> Project: Hadoop Common
> 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.
