hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vivek Ratan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4522) Capacity Scheduler needs to re-read its configuration
Date Mon, 17 Nov 2008 04:12:46 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648075#action_12648075
] 

Vivek Ratan commented on HADOOP-4522:
-------------------------------------

bq. One other difference between the config in the fair scheduler and the capacity scheduler
is that the fair scheduler uses a file different than the Hadoop config file
The Capacity Scheduler also has its own config file. haddop-site.xml, however, contains information
about the queues in the system, which is, or can be, used by all schedulers. 

It's certainly clear that schedulers need to re-read their own config files. It's less clear
whether we want the core Hadoop system to re-read its configuration. If we decide not to,
for the latter, we still need a way for external clients to tell the scheduler re-read its
config. 

Maybe the best thing to do is to add the admin command for reconfiguration, and for now, just
have the JT ask the scheduler to re-read/reconfigure (via a new method in {{TaskScheduler}}).
We could, in separate Jiras, decide whether other config values need to be re-read by the
JT, and add them accordingly. 

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


Mime
View raw message