[
https://issues.apache.org/jira/browse/MAPREDUCE-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Scott Chen updated MAPREDUCE-1198:
----------------------------------
Attachment: MAPREDUCE-1198-v5.patch
1. I have changed mapAssigned and reduceAssigned variables to mapsAssigned and
reducesAssigned.
2. I agree that using the foundTask flag is a better idea. It does make the
code clear and the function is the same. So I also made the change.
3. I still feel bad about creating a new hashmap for every task assigned. So in
this patch there are two hashmap: one for map and the other dummy one for
reduce. I don't know if you like this solution. If you think this is not good,
we can change it back to your proposal.
> Alternatively schedule different types of tasks in fair share scheduler
> -----------------------------------------------------------------------
>
> Key: MAPREDUCE-1198
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1198
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: contrib/fair-share
> Affects Versions: 0.22.0
> Reporter: Scott Chen
> Assignee: Scott Chen
> Fix For: 0.22.0
>
> Attachments: MAPREDUCE-1198-v1.patch, MAPREDUCE-1198-v2.patch,
> MAPREDUCE-1198-v3.patch, MAPREDUCE-1198-v4.patch, MAPREDUCE-1198-v5.patch
>
>
> Matei has mentioned in MAPREDUCE-961 that the current scheduler will first
> try to launch map tasks until canLaunthTask() returns false then look for
> reduce tasks. This might starve reduce task. He also mention that
> alternatively schedule different types of tasks can solve this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
