hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Newman (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5670) Hadoop configurations should be read from a distributed system
Date Fri, 02 Apr 2010 01:29:27 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852633#action_12852633

Alex Newman commented on HADOOP-5670:


This is really exciting as I feel currently  that configs are a hard problem. Currently it
can be difficult to get transparency and flexibility depending on the configs scope. Specifically,
where do I audit if a user sets a particular job paramater, or an admin sets a paramater for
a particular system. It seems that this jira is about setting up scope on a cluster wide basis.
LDAP and Zookeeper could allow configs across clusters. 

This is something that gasp vms logicals got right IMO in that it is one interface to solve
all of these problems. I think one giant key value store is a good first step, but realistically
you need different permissions based on if you are making a change intra cluster, inter cluster,
for one box, for one user or for one job. Being able to go back and see what the hierarchy
of those values, and having them being centrally managed would be really neat. Just my two
cents, I am just spoiled from my slow big machines.

> 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,

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message