[
https://issues.apache.org/jira/browse/MAPREDUCE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12751777#action_12751777
]
Matei Zaharia commented on MAPREDUCE-944:
-----------------------------------------
+1 looks good to me, except for one minor detail: I'd change the JavaDoc on
canLaunchTask from "Can a given {...@link TaskTracker} run another new task?"
to "Can a given {...@link TaskTracker} run another new task from a given job?
This method is provided for use by LoadManagers that take into account jobs'
individual resource needs when placing tasks." This way the purpose of the
method, and its difference from canAssignMap/canAssignReduce, is better
explained. It might also be good to look at the comments for
canAssignMap/Reduce and make them say that these methods are used to check
whether any attempt to find a job with maps/reduces should be made.
> Extend FairShare scheduler to fair-share memory usage in the cluster
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-944
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-944
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/fair-share
> Reporter: dhruba borthakur
> Attachments: LoadManager.txt
>
>
> The FairShare Scheduler has an extensible LoadManager API to regulate
> allocating new tasks on a particular TaskTracker. In similar lines, it would
> be nice if the FairShare Scheduler can have a pluggable policy to regulate
> new tasks from a particular job. This will allow one to skip scheduling tasks
> of a job that is eating a large percentage of memory in the cluster, i.e.
> fair-share of memory resources among jobs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
