[
https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647425#action_12647425
]
Owen O'Malley commented on HADOOP-4522:
---------------------------------------
{quote}
We'd thought of the same approach for the Capacity Scheduler, but one big
problem is that the Scheduler may read the config file while it is in the
middle of being changed.
{quote}
+1
I think the best trade-off is having an admin command that gets the job tracker
to re-read all of its config files, including a call down to the scheduler to
re-read its config file. Maybe something like:
{code}
bin/hadoop mapred-admin -reconfigure
{code}
> 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.
