Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A3F85CAB5 for ; Thu, 13 Jun 2013 18:13:20 +0000 (UTC) Received: (qmail 20112 invoked by uid 500); 13 Jun 2013 18:13:20 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 20078 invoked by uid 500); 13 Jun 2013 18:13:20 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 20068 invoked by uid 99); 13 Jun 2013 18:13:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Jun 2013 18:13:20 +0000 Date: Thu, 13 Jun 2013 18:13:20 +0000 (UTC) From: "Alejandro Abdelnur (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-803) factor out scheduler config validation from the ResourceManager to each scheduler implementation 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/YARN-803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13682495#comment-13682495 ] Alejandro Abdelnur commented on YARN-803: ----------------------------------------- Zhijie, On adding the setConf() method to the scheduler API, it is up to the scheduler impl to use or not the Yarn configuration. If a scheduler impl decides to do so, by implementing Configurable it will get it. I've initially thought about adding a validateConf() method to the scheduler API. I've decided to go the Configurable route for the reason above. Because of that, I think we should do things as in the current patch. > factor out scheduler config validation from the ResourceManager to each scheduler implementation > ------------------------------------------------------------------------------------------------ > > Key: YARN-803 > URL: https://issues.apache.org/jira/browse/YARN-803 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager, scheduler > Affects Versions: 2.0.4-alpha > Reporter: Alejandro Abdelnur > Assignee: Alejandro Abdelnur > Attachments: YARN-803.patch > > > Per discussion in YARN-789 we should factor out from the ResourceManager class the scheduler config validations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira