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 C1A8D100DD for ; Thu, 1 Aug 2013 06:41:56 +0000 (UTC) Received: (qmail 91742 invoked by uid 500); 1 Aug 2013 06:41:56 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 91709 invoked by uid 500); 1 Aug 2013 06:41:56 -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 91440 invoked by uid 99); 1 Aug 2013 06:41:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Aug 2013 06:41:54 +0000 Date: Thu, 1 Aug 2013 06:41:54 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1004) yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler 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-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726124#comment-13726124 ] Sandy Ryza commented on YARN-1004: ---------------------------------- By which I mean [~tucu00] > yarn.scheduler.minimum|maximum|increment-allocation-mb should have scheduler > ---------------------------------------------------------------------------- > > Key: YARN-1004 > URL: https://issues.apache.org/jira/browse/YARN-1004 > Project: Hadoop YARN > Issue Type: Improvement > Components: scheduler > Affects Versions: 2.1.0-beta > Reporter: Sandy Ryza > Attachments: YARN-1004.patch > > > As yarn.scheduler.minimum-allocation-mb is now a scheduler-specific configuration, and functions differently for the Fair and Capacity schedulers, it would be less confusing for the config names to include the scheduler names, i.e. yarn.scheduler.fair.minimum-allocation-mb, yarn.scheduler.capacity.minimum-allocation-mb, and yarn.scheduler.fifo.minimum-allocation-mb. > The same goes for yarn.scheduler.increment-allocation-mb, which only exists for the Fair Scheduler, and yarn.scheduler.maximum-allocation-mb, for consistency. > If we wish to preserve backwards compatibility, we can deprecate the old configs to the new ones. -- 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