Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 19 Mar 2013 05:29:15 +0000 (UTC)
From: "Karthik Kambatla (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12636650.1363120452738.9528.1363670955525@arcas>
In-Reply-To: <JIRA.12636650.1363120452738@arcas>
References: <JIRA.12636650.1363120452738@arcas>
Subject: [jira] [Updated] (YARN-469) Make scheduling mode in FS pluggable
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/YARN-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla updated YARN-469:
----------------------------------

    Attachment: yarn-469.patch

Thanks for your review, Alejandro. 

Uploading a new patch that
# Re-uses the scheduling mode instances instead of creating a new instance for every queue using guava caches
# Addresses Alejandro's first 2 comments (nits)
# Configures SchedulingMode.DEFAULT_MODE to defaultSchedulingMode

Will address Alejandro's last point about non-leaf queue in YARN-482 that adds the ability to configure intermediate queues.
                
> Make scheduling mode in FS pluggable
> ------------------------------------
>
>                 Key: YARN-469
>                 URL: https://issues.apache.org/jira/browse/YARN-469
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.0.3-alpha
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>              Labels: scheduler
>         Attachments: yarn-469.patch, yarn-469.patch, yarn-469.patch
>
>
> Currently, scheduling mode in FS is limited to Fair and FIFO. The code typically has an if condition at multiple places to determine the correct course of action.
> Making the scheduling mode pluggable helps in simplifying this process, particularly as we add new modes (DRF in this case).

--
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