[
https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratan updated HADOOP-4522:
--------------------------------
Attachment: 4522.1.patch
Attaching patch (4522.1.patch) which does the following:
* Adds a new method to JobSubmissionProtocol.java:
{code}
/**
* Makes the JT re-read (some of) its configuration.
* @throws IOException
*/
public void reconfigure() throws IOException;
{code}
* JT's implementation currently asks the schedulers do re-read their config.
* Added a corresponding new method to TaskScheduler.java that does nothing by
default:
{code}
/**
* Re-read configuration
* @throws IOException
*/
public void reconfigure() throws IOException {
// do nothing
}
{code}
* implemented re-reading of config file for Capacity Scheduler. The following
config params can be updated for each queue:
** guaranteed capacity
** user limit
** reclaim time limit
* In addition, the following config params can be updated for the scheduler:
** reclaim capacity interval
* As discussed earlier, added a command to mapred-admin to force the JT to
reconfigure:
{code}
bin/hadoop mapred-admin -reconfigure
{code}
* Removed code from CapacitySchedulerConf.java that was added earlier to
support re-reading
* Added test cases
While the changes are not very substantial in terms of lines of code, they do
change the JobSubmission protocol and the TaskScheduler class.
> Capacity Scheduler needs to re-read its configuration
> -----------------------------------------------------
>
> Key: HADOOP-4522
> URL: https://issues.apache.org/jira/browse/HADOOP-4522
> Project: Hadoop Core
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
