Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 80360 invoked from network); 6 Apr 2010 17:53:56 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 Apr 2010 17:53:56 -0000 Received: (qmail 59088 invoked by uid 500); 6 Apr 2010 17:53:56 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 59060 invoked by uid 500); 6 Apr 2010 17:53:56 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 59052 invoked by uid 99); 6 Apr 2010 17:53:56 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 17:53:56 +0000 X-ASF-Spam-Status: No, hits=-1231.3 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Apr 2010 17:53:54 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DEE46234C4D8 for ; Tue, 6 Apr 2010 17:53:34 +0000 (UTC) Message-ID: <1371339222.19951270576414912.JavaMail.jira@brutus.apache.org> Date: Tue, 6 Apr 2010 17:53:34 +0000 (UTC) From: "Allen Wittenauer (JIRA)" To: common-issues@hadoop.apache.org Subject: [jira] Commented: (HADOOP-5670) Hadoop configurations should be read from a distributed system MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12854083#action_12854083 ] Allen Wittenauer commented on HADOOP-5670: ------------------------------------------ bq. it would require organizations not using ldap to run additional infrastructure to solve a problem which could be solved by something already provided by the hadoop infrastructure. I would feel as though if we saw many users deploying a isolated ldap installation just for hadoop that we would have made people's life harder not easier. If you s,LDAP,ZK,g above, you'll find it is a better fit. The cold, hard reality is that LDAP is everywhere, ZK is not. There are some key features in ZK that are/were missing in order for it to fit here (with the good news being that those gaps are slowly closing). But the truth of the matter is that LDAP is a well understood technology by most IT departments and ZK is not. (Sidenote: it would be interesting to know how well used the security components of ZK are...) Also, I don't think you should think of ZK as part of the Hadoop infrastructure. It is a sub project (and therefore part of the ecosystem), but you can run Hadoop without using ZK and many many many people do, including Yahoo! for years. bq. Allen, sorry to be a pain , but could you be a bit more pedantic about what you mean by configurations ? Do you think a hybrid system may make sense here? I'll try and write/diagram something up with a concrete proposal as to how I think this should be done, based on conversations I've had with Owen and others over the years. You'll find I'm thinking way beyond just a simple 10 node grid. :) > 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.