Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 2 Feb 2017 01:13:51 +0000 (UTC)
From: "Jonathan Hung (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13024651.1480560647000.13212.1485998031653@Atlassian.JIRA>
In-Reply-To: <JIRA.13024651.1480560647000@Atlassian.JIRA>
References: <JIRA.13024651.1480560647000@Atlassian.JIRA> <JIRA.13024651.1480560647280@jira-lw-us.apache.org>
Subject: [jira] [Updated] (YARN-5951) Changes to allow CapacityScheduler to
 use configuration store
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Feb 2017 01:13:56 -0000


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

Jonathan Hung updated YARN-5951:
--------------------------------
    Attachment: YARN-5951-YARN-5734.002.patch

> Changes to allow CapacityScheduler to use configuration store
> -------------------------------------------------------------
>
>                 Key: YARN-5951
>                 URL: https://issues.apache.org/jira/browse/YARN-5951
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Jonathan Hung
>            Assignee: Jonathan Hung
>         Attachments: YARN-5951-YARN-5734.001.patch, YARN-5951-YARN-5734.002.patch
>
>
> EDIT: changing this ticket. Found that the CapacityStoreConfigurationProvider is not necessary, since we can just grab a Configuration object from StoreConfigurationProvider with type "SCHEDULER" and create a CapacitySchedulerConfiguration from it.
> This ticket will track changes needed for integrating other components to be used by the capacity scheduler.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org