[
https://issues.apache.org/jira/browse/HADOOP-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12557757#action_12557757
]
Arun C Murthy commented on HADOOP-2573:
---------------------------------------
I'd like to throw *job priority* into this festering pool...
At least changing the job-priority (done by the cluster-admin) should in a
change in number of max_slots... thoughts?
> limit running tasks per job
> ---------------------------
>
> Key: HADOOP-2573
> URL: https://issues.apache.org/jira/browse/HADOOP-2573
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Reporter: Doug Cutting
> Fix For: 0.17.0
>
>
> It should be possible to specify a limit to the number of tasks per job
> permitted to run simultaneously. If, for example, you have a cluster of 50
> nodes, with 100 map task slots and 100 reduce task slots, and the configured
> limit is 25 simultaneous tasks/job, then four or more jobs will be able to
> run at a time. This will permit short jobs to pass longer-running jobs.
> This also avoids some problems we've seen with HOD, where nodes are
> underutilized in their tail, and it should permit improved input locality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
