Return-Path: Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: (qmail 98823 invoked from network); 12 May 2010 14:27:23 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 May 2010 14:27:23 -0000 Received: (qmail 26081 invoked by uid 500); 12 May 2010 14:27:23 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 26041 invoked by uid 500); 12 May 2010 14:27:22 -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 26026 invoked by uid 99); 12 May 2010 14:27:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 14:27:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 May 2010 14:27:20 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o4CEQwQP020931 for ; Wed, 12 May 2010 14:26:58 GMT Message-ID: <27861068.25891273674418076.JavaMail.jira@thor> Date: Wed, 12 May 2010 10:26:58 -0400 (EDT) From: "Edward Capriolo (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 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-5670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866582#action_12866582 ] Edward Capriolo commented on HADOOP-5670: ----------------------------------------- Jeff the implementation I want to go for was described above: I suppose if all we wish is to replace basically the -D options passed into hadoop, then I am very openminded to a ldap based scheme as a plugin. I would be very happy if it included some scoping so that configuration could be provided on a intra cluster, inter cluster, host ,user or job level. Guidelines should be provided as how not to disrupt existing ldap users. And meet this requirement: I think we don't need to debate hard on ldap versus zookeeper versus etc on this specific issue. I assume that we would have the abstraction here so that folks can try out different systems - ldap, zookeeper etc. and can configure one as per their environment needs. Also I wanted to add that since the new hadoop security is kerberos. Kerberos is normally backended by LDAP, so a good point of users will have an ldap server at their disposal. > 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.