[
https://issues.apache.org/jira/browse/HADOOP-4854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hemanth Yamijala updated HADOOP-4854:
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.20.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I just committed this to trunk and the Hadoop 0.20 branch. Thanks, Sreekanth !
I have only committed the documentation source (the xml files), and not the
generated Forrest documentation following the new practice for committing
documentation
> Capacity Scheduler should read the reclaim-capacity-interval config value
> from its own config file
> --------------------------------------------------------------------------------------------------
>
> Key: HADOOP-4854
> URL: https://issues.apache.org/jira/browse/HADOOP-4854
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Vivek Ratan
> Assignee: Sreekanth Ramakrishnan
> Priority: Minor
> Fix For: 0.20.0
>
> Attachments: HADOOP-4854-1.patch, HADOOP-4854-2.patch,
> HADOOP-4854-3.patch, HADOOP-4854-4.patch, HADOOP-4854-5.patch
>
>
> The Capacity Scheduler needs to know the time interval for checking whether
> capacity needs to be reclaimed. This is represented by the static variable
> RECLAIM_CAPACITY_INTERVAL. This value is currently read as follows:
> {code}
> RECLAIM_CAPACITY_INTERVAL =
> conf.getLong("mapred.capacity-scheduler.reclaimCapacity.interval", 5);
> {code}
> This is incorrect for the following reasons:
> * ""mapred.capacity-scheduler.reclaimCapacity.interval" is not present in any
> of the config files: hadoop-site.xml or capacity-scheduler.xml.
> * "mapred.capacity-scheduler.reclaimCapacity.interval" should be specified in
> the scheduler's config file, capacity-scheduler.xml. It should be read
> through org.apache.hadoop.mapred.CapacitySchedulerConf.
> * The Forrest documentation for the Capacity Scheduler should describe this
> setting. We should probably create a new sub-section under 'Configuration',
> titled 'Configuring properties for the Scheduler'.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
