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 06:44:44 GMT

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

Vivek Ratan commented on HADOOP-4522:

bq. is there some part of the system other than the scheduler that needs to look at queues?

bq. Beyond scheduling, has there been a need to have the system re-read its configuration?

Access control for queues (whether queues can accept jobs from particular users) is system-wide
and independent of schedulers. I think we'll want to support dynamic updates to access control
sooner than later. You'll certainly want to add new users or remove users from a queue's access
control fairly often. You probably don't want to restart the JT each time you want to make
such a change. 

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

View raw message