[
https://issues.apache.org/jira/browse/MAPREDUCE-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935568#action_12935568
]
Matei Zaharia commented on MAPREDUCE-2198:
------------------------------------------
Do setup and cleanup tasks do a significant amount of work? I can see two
simple ways of dealing with them other than moving control to the scheduler:
Either always allow them to run (even if the TT is full on map and reduce
slots), or allow them to run but limit the number of such tasks per node to 1
(i.e. have a "setup slot"). If they do need to do CPU-intensive work, then it
makes sense to give control of them to the scheduler.
> Allow FairScheduler to control the number of slots on each TaskTracker
> ----------------------------------------------------------------------
>
> Key: MAPREDUCE-2198
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2198
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Components: contrib/fair-share
> Affects Versions: 0.22.0
> Reporter: Scott Chen
> Assignee: Scott Chen
> Fix For: 0.22.0
>
>
> We can set the number of slots on the TaskTracker to be high and let
> FairScheduler handles the slots.
> This approach allows us to change the number of slots on each node
> dynamically.
> The administrator can change the number of slots with a CLI tool.
> One use case of this is for upgrading the MapReduce.
> Instead of restarting the cluster, we can run the new MapReduce on the same
> cluster.
> And use the CLI tool to gradually migrate the slots.
> This way we don't lost the progress fo the jobs that's already executed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
