Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1652309364.1213599705104.JavaMail.jira@brutus>
Date: Mon, 16 Jun 2008 00:01:45 -0700 (PDT)
From: "Hemanth Yamijala (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3479) Implement configuration items
 useful for Hadoop resource manager (v1)
In-Reply-To: <780180100.1212411465009.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605208#action_12605208 ] 

Hemanth Yamijala commented on HADOOP-3479:
------------------------------------------

I looked at HADOOP-24 in detail. IMO, I feel there are 2 different issues we are discussing in these two JIRAs:

- What HADOOP-24 described and concluded was to provide a way to read Configuration from multiple data sources, including files, LDAP etc. and separate the issue of filling up Configuration from a source (aka ConfSource approach) from answering queries of Configuration itself, which is the Configuration clas.
- What we are trying to evaluate here is whether the configuration format (rather than it's source) be made generic enough to support a very generalized structure of configuration - multiple hierarchies, named groups, etc.

For doing a good job of the latter, IMO, we should just try and define a format that fits the current Hadoop configuration and the new Resource Manager configuration, if at all. Trying to build something too generic without fully understanding what else is required may not work at this level.

Even there, I feel like going with my original proposal of a separate configuration for the resource manager part. We are still figuring out with how the resource management functionality all turns out. If our attempts work well, then we can always refactor to make the Configuration class capable of handling both formats. Then we can make the ResourceManagerConf I defined in the patch a sub-class of the main Configuration class, and reuse the code.
 
Comments from others on this issue ? 

> Implement configuration items useful for Hadoop resource manager (v1)
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-3479
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3479
>             Project: Hadoop Core
>          Issue Type: New Feature
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>         Attachments: 3479.patch
>
>
> HADOOP-3421 lists requirements for a new resource manager for Hadoop. Implementation for these will require support for new configuration items in Hadoop. This JIRA is to define such configuration, and track it's implementation.

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