[
https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643564#action_12643564
]
dhruba borthakur commented on HADOOP-4522:
------------------------------------------
> Changes to the config file need to be atomic for this approach to work
> correctly,
I agree. The FairShare scheduler re-reads the config and if-and-only-if it can
parse the entire file does it accept the new configuration. It works for us,
but if a set of new parameters need to take effect atomically, then there
could be a problem.
> 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.
