[
https://issues.apache.org/jira/browse/HADOOP-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12647775#action_12647775
]
dhruba borthakur commented on HADOOP-4522:
------------------------------------------
The one other case of re-reading the config file is for JT or NN failover.
Suppose, the machine on which my JT was running dies, and I want to make the
running TaskTrackers start communicating with the new JT on a different
machine. This requires the TTs to re-read the config file.
> 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.
