You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Hemanth Yamijala (JIRA)" <ji...@apache.org> on 2009/07/06 09:56:15 UTC
[jira] Resolved: (MAPREDUCE-532) Allow admins of the Capacity
Scheduler to set a hard-limit on the capacity of a queue
[ https://issues.apache.org/jira/browse/MAPREDUCE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hemanth Yamijala resolved MAPREDUCE-532.
----------------------------------------
Resolution: Fixed
Fix Version/s: 0.21.0
Assignee: rahul k singh
Release Note: Provided ability in the capacity scheduler to limit the number of slots that can be concurrently used per queue at any given time.
Hadoop Flags: [Reviewed]
I just committed this to trunk. Thanks, Rahul !
> Allow admins of the Capacity Scheduler to set a hard-limit on the capacity of a queue
> -------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-532
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-532
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: contrib/capacity-sched
> Reporter: Rajiv Chittajallu
> Assignee: rahul k singh
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-532-1.patch, MAPREDUCE-532-2.patch, MAPREDUCE-532-3.patch, MAPREDUCE-532-4.patch, MAPREDUCE-532-5.patch, MAPREDUCE-532-6.patch, MAPREDUCE-532-7.patch
>
>
> For jobs which call external services, (eg: distcp, crawlers) user/admin should be able to control max parallel tasks spawned. There should be a mechanism to cap the capacity available for a queue/job.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.