Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Mon, 21 Jul 2014 16:38:38 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12407253.1225082853790.9757.1405960718958@arcas>
In-Reply-To: <JIRA.12407253.1225082853790@arcas>
References: <JIRA.12407253.1225082853790@arcas>
Subject: [jira] [Resolved] (HADOOP-4522) Capacity Scheduler needs to re-read
 its configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Allen Wittenauer resolved HADOOP-4522.
--------------------------------------

    Resolution: Fixed

Fixed a while back.

> Capacity Scheduler needs to re-read its configuration
> -----------------------------------------------------
>
>                 Key: HADOOP-4522
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4522
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Vivek Ratan
>         Attachments: 4522.1.patch
>
>
> An external application (an Ops script, or some CLI-based tool) can change the configuration of the Capacity Scheduler (change the capacities of various queues, for example) by updating its config file. This application then needs to tell the Capacity Scheduler that its config has changed, which causes the Scheduler to re-read its configuration. It's possible that the Capacity Scheduler may need to interact with external applications in other similar ways. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)