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 "Rajiv Chittajallu (JIRA)" <ji...@apache.org> on 2009/06/30 21:52:47 UTC

[jira] Commented: (MAPREDUCE-532) Option to limit max tasks started per job/queue

    [ https://issues.apache.org/jira/browse/MAPREDUCE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12725770#action_12725770 ] 

Rajiv Chittajallu commented on MAPREDUCE-532:
---------------------------------------------

I would prefer option 1. When we wan't to rate limit, absolute numbers is always good.

> Option to limit max tasks started per job/queue 
> ------------------------------------------------
>
>                 Key: MAPREDUCE-532
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-532
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>            Reporter: Rajiv Chittajallu
>
> 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.