You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Arun C Murthy (Updated) (JIRA)" <ji...@apache.org> on 2011/11/24 08:00:41 UTC
[jira] [Updated] (MAPREDUCE-1872) Re-think (user|queue) limits on
(tasks|jobs) in the CapacityScheduler
[ https://issues.apache.org/jira/browse/MAPREDUCE-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arun C Murthy updated MAPREDUCE-1872:
-------------------------------------
Target Version/s: 0.22.0
Fix Version/s: 0.20.203.0
Konstantin, since you are fixing stuff in the CapacityScheduler (e.g. MAPREDUCE-3026), you might want to port this also. Please take a look, thanks.
> Re-think (user|queue) limits on (tasks|jobs) in the CapacityScheduler
> ---------------------------------------------------------------------
>
> Key: MAPREDUCE-1872
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1872
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/capacity-sched
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.20.203.0
>
>
> We need to re-think our story to have lead to a better overall picture of having limits on {users, queues} w.r.t
> # Jobs - limits on submission, initialization
> # Tasks - limits per-job, per-queue on total tasks, concurrent tasks etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira