[
https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643407#action_12643407
]
Vivek Ratan commented on HADOOP-4522:
-------------------------------------
bq. In the curret code, the Fair Share scheduler periodically checks the
modification time of its configuration file to detect any changes.
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. Changes to the config file need to be atomic for this
approach to work correctly, which seemed too severe a restriction to place.
> 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.
